Subject: Re: syslog_r (Re: CVS commit: src/lib/libc)
To: YAMAMOTO Takashi <firstname.lastname@example.org>
From: Christos Zoulas <email@example.com>
Date: 10/26/2006 06:02:33
On Oct 26, 12:13pm, firstname.lastname@example.org (YAMAMOTO Takashi) wrote:
-- Subject: syslog_r (Re: CVS commit: src/lib/libc)
| > Module Name: src
| > Committed By: christos
| > Date: Wed Oct 25 23:49:31 UTC 2006
| > Modified Files:
| > src/lib/libc: shlib_version
| > src/lib/libc/gen: Makefile.inc syslog.3 syslog.c
| > src/lib/libc/include: namespace.h
| > Log Message:
| > add _r functions for syslog from OpenBSD
| - are you sure if it's signal-safe?
| it seems to involve stdio and even locale stuffs...
| - even if its current implementation is signal-safe,
| i don't think it's a good idea to document syslog_r as signal-safe.
I did not make any such claim, although it appears to be. Yes, the
biggest issue is if we can guarantee that vsnprintf() is signal safe.