thread-unsafe syslog code in libc?

[Robert Watson]

On Sun, 15 Aug 2004, John Polstra wrote:

> The above is only to handle an unusual error case. 
> 
> There is some thread-unsafeness here, but it doesn't look like it would
> matter under normal conditions. 

So maybe we're dealing with a user space race where multiple threads
attempt to do a first syslog in parallel?

Martin -- do we know exactly what that application does threadwise to
generate this problem?

Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
robert at fledge.watson.org      Principal Research Scientist, McAfee Research