![]() | |||||||||||||
Messages in this thread |
On Wednesday 15 March 2006 16:23, linux-os (Dick Johnson) wrote: > > On Wed, 15 Mar 2006, Denis Vlasenko wrote: > > > On Wednesday 15 March 2006 15:14, Andreas Schwab wrote: > >> Stefan Seyfried <seife@suse.de> writes: > >> > >>> any good daemon closes stdout, stderr, stdin > >> > >> A real good daemon would redirect them to /dev/null. > > > > Yeah, yeah, let's first close stderr, and then proceed and > > add some code to handle command line --log=file, and to do > > logging to that file. > > > > Why good ol' fprintf(stderr,...) isn't enough? Why do you > > want to complicate things? > > > > What's so hard in doing "daemon 2>/dev/null &" if you don't > > want to save log? > > -- > > vda > > The daemon needs to have the standard input closed as well as > any I/O connection to a possible terminal. Just closing > standard input, allows a dup() in rogue code to recreate it. > Basically, file-descriptors 0, 1, and 2, need to be USED and > used for something else (like open /dev/null or open "/"). > That's how you prevent rogue code, inserted via overflow or > other means, from obtaining control of your system. ... and everything described above is perfectly doable by shell mechanisms (like redirections) prior to strting daemon, right? -- vda - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2006-03-16 08:10 [from the cache] ©2003-2008 | |||||||||||||