"israel fdez." wrote:
>
> The problem in using std(in, out, err) is that my application is running as a
> daemon,
Running as a daemon and providing interactive I/O are
incompatible goals. A daemon is a program that runs
in the background without a tty.
If you need a way for a user to control your daemon
from the command line, use a regular interactive
program that communicates with the daemon using
some IPC mechanism.
> and what would hapen if the root console is closed once it is
> running, or if the daemon never run in a console (rc.local or something else)?
Write your daemon to be a daemon, and not to care
about TTYs at all. Provide a well-defined IPC
interface via signals, a FIFO, a Unix socket,
an IP socket, shared memory, or whatever.
Cheers,
-- Joe
Any OS distinguishable from Windows is not sufficiently broken.
--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive: http://mail.nl.linux.org/kernelnewbies/
FAQ: http://kernelnewbies.org/faq/
