On 8/16/2023 8:15 AM, Hansa via users wrote:
Hi,
Trying to upgrade Mail::SpamAssassin via cpan but I get "spam_pid not
found" errors (see debug.log).
# ps ax | grep `cat /var/run/spamd.pid
73673 ? Ss 0:04 /usr/bin/perl -T -w /usr/sbin/spamd -d
--pidfile=/run/spamd.pi
ng you do to the operational system configuration that handles
running spamd should have any effect on how the build-time tests work.
The tests are supposed to be fully isolated from the installed instance
of SA, if there is an installed instance of SA.
t/sa_check_spamd.t spam_pid
What do you exactly mean by "removing the option in the startup unit"?
I'm not running spamd via a socket.
I commented out "PIDFILE="/var/run/spamd.pid" in default/spamassassin.
Test still results in timeout.
t/sa_check_spamd.t .... spam_pid not f
Unfortunately this is not the solution.
/run/spamd.pid exists and contains the same pid as /var/run/spamd.pid.
It is created when starting the spamd service.
On 16-08-2023 14:34, bOnK wrote:
# ps ax | grep `cat */var/run/spamd.pid *
73673 ? Ss 0:04 /usr/bin/perl -T -w /usr/sbin/
Hi,
Trying to upgrade Mail::SpamAssassin via cpan but I get "spam_pid not
found" errors (see debug.log).
# ps ax | grep `cat /var/run/spamd.pid
73673 ? Ss 0:04 /usr/bin/perl -T -w /usr/sbin/spamd -d
--pidfile=/run/spamd.pid --create-prefs --max-children 5
--helpe
