[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: bug in openlog()
From: |
Christopher Allen Wing |
Subject: |
Re: bug in openlog() |
Date: |
Fri, 21 Dec 2001 17:28:51 -0500 (EST) |
Ulrich:
> > I guess that my opinion is it wouldn't hurt to change the internal
> > behavior of syslog() for consistency.
>
> Of course it can hurt. Somebody might depend on this behavior. It's
> just like putenv(), the user can change the string afterwards.
Sure, but that wouldn't be threadsafe, so it would defeat all the nice
locking you added in the syslog routines :)
> Live with it and if you want the documentation to be clearer send a
> patch. There will be no code change.
I sent a proposed update to the documentation in my last e-mail:
http://www.engin.umich.edu/caen/systems/Linux/code/patches/glibc-2.2.4-manual.patch
If you don't want to follow the URL, let me know and I'll send you an
e-mail with the patch in the text body.
Thanks,
Chris Wing
address@hidden