You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Justin Mason <jm...@jmason.org> on 2006/12/14 11:37:05 UTC

Re: SpamdForkScaling messages?

snowcrash+spamassassin writes:
> i have
> 
> 	spamassassin --version
> 		SpamAssassin version 3.1.8-r454679
> 			  running on Perl version 5.8.8
> 
> in my debug-level spamd log i see frequently repeating instances of,
> 
> Wed Dec 13 18:36:13 2006 [923] dbg: prefork: periodic ping from spamd parent
> Wed Dec 13 18:36:13 2006 [923] dbg: prefork: sysread(9) not ready,
> wait max 300 secs
> Wed Dec 13 18:36:13 2006 [923] dbg: prefork: periodic ping from spamd parent
> Wed Dec 13 18:36:13 2006 [923] dbg: prefork: sysread(9) not ready,
> wait max 300 secs
> ...
> 
> grep'ing in src, i note that these errors originate in,
> 
> 	SpamdForkScaling.pm
> 
> afaict, there's no, manpage available for Mail::SpamAssassin::SpamdForkScaling
> 
> searching on the website, i find links to the .pm src.
> 
> both TITLE & FULLTEXT searches on the wiki come up empty.
> 
> 	what is SpamdForkScaling? are there docs?
> 	are these "not ready" messages a problem?
> 	if so, wht do i do about them?

They're debug messages -- not a problem at all.

--j.

Re: SpamdForkScaling messages?

Posted by snowcrash+spamassassin <sc...@gmail.com>.
> They're debug messages -- not a problem at all.

great. i can ignore them. :-)

does it matter at all that those message have DISappeared after
switching from sa-via-TCP-sock to sa-via-UNIX-sock?