Quote:
Originally Posted by LittleRedRooster
A process that has been started without controlling tty (like those by initd)
cannot be connected to a tty afterwards, but most init processes write to syslog,
so your best bet is the syslog-ng config file to direct the output of this
process to a tty where you can read it.
Theo
|
Thanks for the help, but in my situation this is not a chance. My application opens an embeded telnet connection with the machine which host the process. I log as root in the telnet tty, so I have no rights problem but the host system is an linux embeded machine so I can not modify any file on it (for guarantee purposes) and that system does not use any syslog like stuff that I can read. Its a minimal system.
Thanks again LittleRedRooster.
PD: Sorry for my poor english