Amavis::IO::RW: Error flushing on close

[Mark Martinec]

> Stefan,
> 
> > I just updated to version 2.7.1 and experience this error with
> > $log_level=2:
> > 
> > amavis[24809]: (24809-03) Sophie broken pipe (don't worry), retrying (1)
> > amavis[24809]: (24809-03) Amavis::IO::RW: Error flushing on close: Error
> > writing to socket: Broken pipe at /usr/sbin/amavisd line 6876,
[...]
> I checked the code, and it is alright, nothing to worry about.
> An extra check for a status of a flush before a close was added and
> an error during a flush() is now logged separately at log level 1,
> while previously this log entry was not there, just the final
> outcome of a close() was tested and reported.

To avoid the logging clutter at log level 1 or above, the following
trivial patch may be applied to 2.7.1, which just reduces a log level
for this innocent but sinister-looking message to 5.

The 2.8.0 will bring a more selective solution, differentiating
between this error on a regular close, from the same on a DESTROY.

  Mark
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0.patch
Type: text/x-patch
Size: 351 bytes
Desc: not available
URL: <http://lists.amavis.org/pipermail/amavis-users/attachments/20120518/1aff4a54/attachment.bin>