#1063758 spamd: /etc/init.d/spamd still uses --name instead of --exec

Package:
spamd
Source:
spamd
Submitter:
Alessandro Vesely
Date:
2024-04-25 10:18:02 UTC
Severity:
normal
Tags:
#1063758#5
Date:
2024-02-12 09:42:31 UTC
From:
To:
Dear Maintainer,

/etc/init.d/spamd still uses --name instead of --exec.
This is noticeable on shutdown, what the system waits
for some time trying to kill spamd, and then complains
something about its inability to track process names
and suggests to use --exec injstead.

Best
Ale
#1063758#10
Date:
2024-04-02 18:03:32 UTC
From:
To:
Control: tags -1 + moreinfo
the following package versions:

ii  init-system-helpers 1.65.2       all          helper tools for all init systems
ii  spamd               4.0.0-6      all          Server for SpamAssassin spam filtering daemon
ii  sysvinit-core       3.06-4       amd64        System-V-like init

When stopping spamd, there is no indication of any delay or other issue
terminating spamd.

Manual termination:
root@debian-sysv:~# /etc/init.d/spamd status
spamd is running.
root@debian-sysv:~# /etc/init.d/spamd stop
Stopping SpamAssassin Mail Filter Daemon: spamd.
root@debian-sysv:~# /etc/init.d/spamd status
spamd is not running ... failed!

Console output on shutdown:
root@debian-sysv:~# /etc/init.d/spamd status
spamd is running.
root@debian-sysv:~# shutdown -h now
...
Stopping SpamAssassin Mail Filter Daemon: spamd.
...

What is the specific warning you're seeing?  Is spamd actually running
when the init script is executing?

noah
#1063758#17
Date:
2024-04-14 12:09:05 UTC
From:
To:

Sorry for the delay.  Today a new kernel image was loaded, so I had to reboot.
I attach a screenshot of the closing session.  Near the bottom, it says:

Stopping S.M.A.R.T. daemon smartd.
Stopping SpamAssassin Mail Filter Daemon spamd.
start-stop-daemon: warning: this system is not able to track process names
longer than 15 characters. please use --exec instead of --name.

Next it hangs there for several seconds (~30).  The next string says:

Asking all remaining processes to terminate...done.

Is it not SpamAssassin causing that warning?


Best
Ale
#1063758#22
Date:
2024-04-23 16:39:00 UTC
From:
To:
If it is, it doesn't do it on Debian.  Even with sysvinit, though, the
stop jobs during shutdown run in parallel, so that message may be coming
from somewhere else.

If you manually stop spamassassin with `/etc/init.d/spamd stop`, do you
get the same warning?

noah
#1063758#27
Date:
2024-04-24 08:02:47 UTC
From:
To:

Good question!  No, I don't.  It stops cleanly and quickly.

Sorry for the noise.
Ale
#1063758#32
Date:
2024-04-24 16:47:42 UTC
From:
To:
You may need to stop/start each service individually to find the
culprit.  We can reassign this bug accordingly when you do.

noah
#1063758#37
Date:
2024-04-25 10:14:54 UTC
From:
To:
Hm... I tried the two immediately preceding (K57)smartd, which happen to be
smartmontools and rpcbind, and they also work well.

I have /etc/init.d/.legacy-bootordering, so scripts should run one at a time.
Is it possible that the start/ stop functions work differently when many
daemons have been stopped?

BTW, there are several scripts using --name; I have:
# grep -l -- --name /etc/init.d/* | wc -l
21
# grep -l -- --exec /etc/init.d/* | wc -l
37


Best
Ale