On Thursday 16 May 2002 11:47 pm, drieux wrote:
[snip]
> the problem is that it closes both stdin and stderr, which are
> used by other things we play with and need to be appropriately
> reopened to some place other than the terminal we are no
> longer talking to...
>
> I'm all in favor of cluttering up syslog with JUNK - but most
> of the decent sysAdds will allow that over my dead body....
> {they never say, 'over my dead body' - they always say it
> expressly as 'Right, yeah sure, over your dead body that's gonna happen'}Just out of interrest, what do they have against using the syslog facility? It gives a very good pre-defined way of controlling log entries. Using the syslog.conf you could filter out your messages to a seperate file, or even to a seperate machine. Also, whay would stop you from just re-opening the STD[IN|OUT|ERR] handles to files in the root FS anyway? (I've not looked at the link provided and I've never done any daemon work, I'm just interrested) [snip] -- Gary Stainburn This email does not contain private or confidential material as it may be snooped on by interested government parties for unknown and undisclosed purposes - Regulation of Investigatory Powers Act, 2000 -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
