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 vitaly
Recipients vitaly
Date 2012-10-08.22:09:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1349734153.29.0.505405223555.issue16168@psf.upfronthosting.co.za>
In-reply-to
Content
SOCK_DGRAM causes log messages larger than about 2000 bytes to be dropped altogether on MacOS X 10.7.5 and to be truncated to 2081 bytes on Linux (tested with Amazon's linux, which is based on centos). This is quite unfortunate, since many exception tracebacks for production apps are larger than 2000 bytes, and it's paramount to capture the entire traceback in order to debug the issue. This limitation can be overcome if _connect_unixsocket() used the socktype arg value that was passed to SysLogHandler constructor.
History
Date User Action Args
2012-10-08 22:09:13vitalysetrecipients: + vitaly
2012-10-08 22:09:13vitalysetmessageid: <1349734153.29.0.505405223555.issue16168@psf.upfronthosting.co.za>
2012-10-08 22:09:13vitalylinkissue16168 messages
2012-10-08 22:09:13vitalycreate