The problem in using std(in, out, err) is that my application is running as a daemon, 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)? I'm not a Linux programming guru, so... sorry if you are telling something evident and I don't get your point!!! :) best reg@rds israel On Monday 13 May 2002 02:26 pm, you wrote: > On Mon, May 13, 2002 at 02:06:10PM -0400, israel fdez. wrote: > > My question isn't about kernel programming but is abour Linux > > programming. I need a daemon to write to the avtive console, and I need > > more, I need to wait for a user answer, but I don't know how to find the > > right one, I've tried writing to /dev/conole and /dev/tty0 but no > > results. > > Israel, I'm afraid you may have incompatible goals with the setups of > most Linux boxes. Consider that consoles aren't needed on many machines. > Consider that on many machines, serial is the only console available. > Other systems use vga console, others use framebuffer console, and many > boot into X in a real hurry, masking whatever console used to be there. > > If you want to write to the physical console, your best bet may be to > use syslog, as configured by syslog.conf(5). If you really want > interactive responses, why not just use the stdin, stdout, and stderr > that your program was passed when it was exec()ed? That will work no > matter if the program was started on a console, over telnet, or ssh. -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
