This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author petri.lehtinen
Recipients Carl.Crowder, petri.lehtinen, r.david.murray, vinay.sajip
Date 2011-05-25.16:06:56
SpamBayes Score 8.33208e-06
Marked as misclassified No
Message-id <20110525160655.GI10448@colossus>
In-reply-to <316848.62625.qm@web25806.mail.ukl.yahoo.com>
Content
Vinay Sajip wrote:
> @Petri: It's great that it worked for you, but IIRC the syslog module has had 
> thread-safety issues at least on some platforms, which is why it's not used in 
> the SysLogHandler implementation (disclaimer: this was a while ago, I don't know 
> if the syslog module is thread-safe now - I believe the thread-safety issues 
> were in the underlying C APIs).

Ah, I was not aware of thread safety issues. A quick search revealed
that there has been a non-standard syslog_r() function that's thread
safe, but nowadays POSIX requires syslog() to be thread safe, too.
History
Date User Action Args
2011-05-25 16:06:57petri.lehtinensetrecipients: + petri.lehtinen, vinay.sajip, r.david.murray, Carl.Crowder
2011-05-25 16:06:56petri.lehtinenlinkissue12168 messages
2011-05-25 16:06:56petri.lehtinencreate