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 vinay.sajip
Recipients josm, luke-jr, vinay.sajip
Date 2007-09-27.06:19:25
SpamBayes Score 0.015154446
Marked as misclassified No
Message-id <1190873965.72.0.633799679989.issue1711603@psf.upfronthosting.co.za>
In-reply-to
Content
It's only a bug when it doesn't work according to design. The present
design seems adequate in that it allows syslogging via UDP or domain
sockets. No one else has asked for the functionality of using system
calls. BTW I note that Metalog's home page says it's a modern
replacement for syslogd and klogd - so one might have reasonably
expected socket support.

You can avoid having to patch Python each time by the simple expedient
of creating a SysLogHandler subclass (a one-time operation) and using it
in place of the included SysLogHandler.
History
Date User Action Args
2007-09-27 06:19:25vinay.sajipsetspambayes_score: 0.0151544 -> 0.015154446
recipients: + vinay.sajip, josm, luke-jr
2007-09-27 06:19:25vinay.sajipsetspambayes_score: 0.0151544 -> 0.0151544
messageid: <1190873965.72.0.633799679989.issue1711603@psf.upfronthosting.co.za>
2007-09-27 06:19:25vinay.sajiplinkissue1711603 messages
2007-09-27 06:19:25vinay.sajipcreate