Re: /dev/stderr gets unlinked 8]

On Wednesday 15 March 2006 15:14, Andreas Schwab wrote:
> Stefan Seyfried <[email protected]> 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: /dev/stderr gets unlinked 8]
    • From: "linux-os \(Dick Johnson\)" <[email protected]>

• References:
  • /dev/stderr gets unlinked 8]
    • From: Denis Vlasenko <[email protected]>
  • Re: /dev/stderr gets unlinked 8]
    • From: Stefan Seyfried <[email protected]>
  • Re: /dev/stderr gets unlinked 8]
    • From: Andreas Schwab <[email protected]>

• Prev by Date: Re: /dev/stderr gets unlinked 8]
• Next by Date: [PATCH] SELinux - cleanup stray variable in selinux_inode_init_security()
• Previous by thread: Re: /dev/stderr gets unlinked 8]
• Next by thread: Re: /dev/stderr gets unlinked 8]
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]