On Sat, Dec 28, 2024 at 22:59:19 +0100, Nicolas George wrote: > Roger Price (12024-12-28): > > ● fetchmail.service - LSB: init-Script for system wide fetchmail daemon > > Loaded: loaded (/etc/init.d/fetchmail; generated) > > Active: inactive (dead) since Sat 2024-12-28 10:37:58 CET; 6h ago > > Docs: man:systemd-sysv-generator(8) > > Process: 1250 ExecStart=/etc/init.d/fetchmail start (code=exited, > > status=0/SUCCESS) > > Process: 1199929 ExecStop=/etc/init.d/fetchmail stop (code=exited, > > status=0/SUCCESS) > > Tasks: 1 (limit: 57750) > > Memory: 1.9M > > CPU: 6min 33.392s > > CGroup: /system.slice/fetchmail.service > > └─1264 /usr/bin/fetchmail -f /etc/fetchmarc > > --pidfile /var/run/fetchmail/fetchmail.pid --syslog > > ... > > Dec 28 17:06:54 titan fetchmail[1264]: reading message > > > > mail...@rogerprice.org@mail.gandi.net:1 of 1 (9321 octets) flushed > > > > It's dead > > It is “dead” but not dead, since it still has a process. Your problem is > there, you do not need to look elsewhere: systemctl stop did not do its > job properly. You need to find out why.
If you look at the ExecStart= there, you can see that this isn't a proper systemd unit. It's just an auto-generated wrapper around the init.d scripts. If an init.d script is broken and doesn't stop the service that it's supposed to stop, well, that's kinda why people stopped using sysv init. It's really terrible. I believe Roger said he's on Debian 11(?). The file list for the Deb12 package shows both an init.d script and a systemd unit file. <https://packages.debian.org/bookworm/amd64/fetchmail/filelist> I don't know whether one of them is just a stub that acts as a wrapper for the other, or whether they're both proper, full-fledged management files for their respective init systems. So, this might be a "bug already fixed in stable" kind of situation.
