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 LwarX
Recipients LwarX, vinay.sajip
Date 2009-07-15.16:19:31
SpamBayes Score 8.83798e-07
Marked as misclassified No
Message-id <>
Which syslog daemon you use?  I've encountered this on syslog-ng. There
is stripped down syslog-ng.conf (messages with facility LOCAL0 are
routed to /var/log/local.log and all others to /var/log/default.log):

options {
        use_dns (no);
        use_fqdn (no);

source src {
        unix-stream("/dev/log" max-connections(256));

template t_filetmpl {
        template("$YEAR-$MONTH-$DAY $HOUR:$MIN:$SEC $HOST $MSG\n");

# Create destinations
destination default { file("/var/log/default.log" template(t_filetmpl) ); };
destination local { file("/var/log/local.log" template(t_filetmpl) ); };

# Create filters
filter local { facility(local0) or program("^root.*"); };

# Connect source and destinations
log { source(src); filter(local); destination(local); flags(final); };
log { source(src); destination(default); };

And this is result:

# first line landed in /var/log/local.log
Jul 15 23:52:02 localhost root: ERROR <module>/14 division by zero

# remaining ones in /var/log/default.log
Jul 15 23:52:02 localhost Traceback (most recent call last):
Jul 15 23:52:02 localhost File "./", line 12, in <module>
Jul 15 23:52:02 localhost a = 1/0
Jul 15 23:52:02 localhost ZeroDivisionError: integer division or modulo
by zero

Results like yours (which are not very readable but still appropriate
for me) I get only when logging performed via udp socket.
Date User Action Args
2009-07-15 16:19:33LwarXsetrecipients: + LwarX, vinay.sajip
2009-07-15 16:19:33LwarXsetmessageid: <>
2009-07-15 16:19:31LwarXlinkissue6444 messages
2009-07-15 16:19:31LwarXcreate