> Well at least in Redhat, if you do systemctl reload postfix it just
> executes postfix reload internally. So it makes absolutely no
> difference.
>
> # cat /usr/lib/systemd/system/postfix.service
> [Unit]
> Description=Postfix Mail Transport Agent
> After=syslog.target network.target
> Conflicts=sendmail.service exim.service
>
> [Service]
> Type=forking
> PIDFile=/var/spool/postfix/pid/master.pid
> EnvironmentFile=-/etc/sysconfig/network
> ExecStartPre=-/usr/libexec/postfix/aliasesdb
> ExecStartPre=-/usr/libexec/postfix/chroot-update
> ExecStart=/usr/sbin/postfix start
> ExecReload=/usr/sbin/postfix reload
> ExecStop=/usr/sbin/postfix stop
>
> [Install]
> WantedBy=multi-user.target
Hmm. My Ubuntu system has no such file.
~$ sudo systemctl status postfix.service
● postfix.service - LSB: Postfix Mail Transport Agent
Loaded: loaded (/etc/init.d/postfix; bad; vendor preset: enabled)
Drop-In: /run/systemd/generator/postfix.service.d
└─50-postfix-$mail-transport-agent.conf
Active: active (running) since Wed 2017-08-09 10:20:02 PDT; 1 day 1h ago
Docs: man:systemd-sysv-generator(8)
Tasks: 4
Memory: 6.5M
CPU: 1.836s
CGroup: /system.slice/postfix.service
├─ 1971 /usr/lib/postfix/sbin/master
├─20028 qmgr -l -t unix -u
├─20030 pickup -l -t unix -u -c
└─20039 tlsmgr -l -t unix -u -c
I'm a newbie to systemd. But I guess the above is telling me that the
postfix.service is auto-generated.
Looking at the file listed in "Drop-In", I don't see the reload command.
$ cat
/run/systemd/generator/postfix.service.d/50-postfix-\$mail-transport-agent.c
onf
# Automatically generated by systemd-insserv-generator
[Unit]
Wants=mail-transport-agent.target
Before=mail-transport-agent.target
The logical assumption would be that the auto-generated service would have
the same commands as "postfix ...".
But I haven't yet figured out how to show/prove whether "postfix reload" =
"systemctl reload postfix"
Michael
