spamd: logger: try using --syslog-socket={unix,inet} or --syslog=file

[Nikolaus Rath]

Hello,

For a couple of weeks now, spamd has been occasionally logging messages
like this:

Aug  4 02:49:58 ebox spamd[5555]: logger: try using --syslog-socket={unix,inet} 
or --syslog=file
Aug  4 02:49:59 ebox spamd[30417]: logger: try using 
--syslog-socket={unix,inet} or --syslog=file

Generally this doesn't seem to happen more than once a day and seems to
coincide with some spamd childs taking exceptionally long to process a
message:

Aug  4 02:48:44 ebox spamd[30417]: spamd: clean message (-6.6/5.0) for 
nobody:107 in 181.4 seconds, 2195 bytes.

Compared to

Aug  4 03:52:12 ebox spamd[5555]: spamd: clean message (-19.2/5.0) for 
nobody:107 in 1.4 seconds, 4242 bytes. 

Also, the messages do *not* show up when spamd starts or reloads (at
least not in the next 5 minutes).

Can anyone tell me what this means?


Best,

   -Nikolaus

-- 
 »Time flies like an arrow, fruit flies like a Banana.«

  PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6  02CF A9AD B7F8 AE4E 425C