On Sat, 2019-11-23 at 13:07 -0600, Jerry Malcolm wrote: > Bob & John.... Thanks so much for the info. But as if I wasn't dazed > & confused enough already, I have discovered a new variable to the > whole thing. I have set up a couple of sandbox EC2 instances just to > play. I didn't realize it at first, but one is AWS Linux 1 and the > other is AWS Linux 2. And the whole startup file structure is > different between the two. The Linux 1 env does indeed have > /etc/init.d/spamassassin. But I don't see anything that looks like > it's setting a user to 'spamd'. In > the Linux 2 env, I have: > > /usr/lib/systemd/system/spamassassin.service that starts > /usr/bin/spamd > using options file /etc/sysconfig/spamassassin > That tells is that the AWS Linux 1 system uses the good old sysVinit system for starting/stopping and controlling system services - its virtually unchanged since it first appeared in Unix SVr4, while the AWS Linux 2 system is using the newer Systemd in its place.
Systemd appeared in RedHat Linux's Fedora (their free distro) a few years back when Fedora 20 was released and is a totally different beast. Its gradually replaced SysvInit in all the main distros since then, so now there only a few sysVinit based Linuxes and these are used by the remaining systemd holdouts. There's a decent documentation set for systemd here: https://www.freedesktop.org/wiki/Software/systemd/ Martin
