Subject: Re: syslog_r (Re: CVS commit: src/lib/libc)
To: SODA Noriyuki <firstname.lastname@example.org>
From: Christos Zoulas <email@example.com>
Date: 10/26/2006 10:06:22
On Oct 26, 11:00pm, firstname.lastname@example.org (SODA Noriyuki) wrote:
-- Subject: Re: syslog_r (Re: CVS commit: src/lib/libc)
| >>>>> On Thu, 26 Oct 2006 09:57:22 -0400,
| email@example.com (Christos Zoulas) said:
| > | Isn't it better to remove syslog_r() from libc as soon as possible,
| > | at least until this issue is settled?
| > | Since leaving it in libc may cause an ABI problem.
| > Why would it cause an ABI issue? the use of vsnprintf() is internal.
| Because maybe we shouldn't have syslog_r() in our libc, and if so,
| removing it causes the ABI problem, if any third party userland
| program begins to use the symbol.
I think that it is useful for a program to be able to syslog()
from an "unsafe" context. What do others think?