thread safe syslog?

[Denis A. Doroshenko]

hello,
i tried to get one thing working, that use rfork(), but although
file tables are private, child and parent still share bss, and
this causes problems. i failed to do some things with syslog,
and now i'm affraid many other possible functions in libc/libwhatever
that may cause such problems.

BTW, in 2.5 i have *much* less problems, than with 2.6, i'm
tracking the cause of the problems ("ktrace -C" hang my box
deadly!).

you may say "hey you with your rfork!don't use it it sucks", but how,
for example, might my threads (libc_r) use syslog, each thread with
different options? is there plans to add some kind of syslog_r to
system (to libc_r?)?

thanks in advance!

--
Denis A. Doroshenko | http://isl.vtu.lt/~cyxob | mailto:cy...@i.am
Omnitel Ltd., Sevcenkos 25, Vilnius 2600, Lithuania

P.S.
i've written syslog_r myself on my home (2.5) box
it works, but it doesn't on 2.6, most probably because of some
/dev/log protocol changes...