syslog disconnection

Bug #142450 reported by Toby Dickenson
2
Affects Status Importance Assigned to Milestone
Zope 2
Invalid
Low
Unassigned

Bug Description

syslog can write to a unix domain socket, usually /dev/log. Bad things happen if the proces listening to this socket (usually syslog) restarts. Some syslog daemons do this often, as part of their log rotation process.

Tags: bug zope
Revision history for this message
Toby Dickenson (htrd) wrote :

Fix is in toby-syslog-reconnect-branch

Consider this for 2.6.1b3 (if there is one) or 2.6.2

Zope 2.7 has a completely different logging system. I must remember to check this when I start looking at 2.7.

Revision history for this message
Toby Dickenson (htrd) wrote :

Status: Accepted => Pending

 Supporters removed: htrd

Unassigning myself.... Im going to have to leave this for someone else.

Tres Seaver (tseaver)
Changed in zope2:
importance: Medium → Low
Revision history for this message
Tres Seaver (tseaver) wrote :

The referenced branch does not exist, and (from what I can tell looking back
at CVS) never did.

In "modern" Zopes, all logging is done either the 'zLOG' package. which is a
thin wrapper on top of the stdlib 'logging' module, or else uses the stdlib
module directly. Any problems with using that module against syslog should
be reported in the Python tracker.

Changed in zope2:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.