7, when sendmail was run in rule-testing mode with -bt, it could be killed witha
Ctrl-C (SIGINT). Beginning with V8.7, SIGINT is handled specially. This allows you to
resume testing whenever something such as a bad DNS lookup takes excessively long to
complete.
14.1.3 SIGKILL
Don??™t kill forcefully sendmail signal
You should never kill sendmail witha SIGKILL (a kill -9). If you do, mail can be lost, or resent
despite successful delivery. Instead, use SIGTERM to stop sendmail.
14.1.4 SIGHUP
Tell sendmail to restart sendmail signal
Beginning withV8.7, a SIGHUP signal will cause sendmail to re-execute itself withits original
command line. This works only if it is running in daemon mode (with -bd, ?§6.7.6 on
page 234). For example, consider initially running sendmail like this:
# /usr/sbin/sendmail -bd -q1h
Then imagine that you changed something in the configuration file and wanted the running
daemon to reread that file. You could cause that to happen by killing the currently running
daemon with a SIGHUP signal:
# kill -HUP `head -1 /etc/mail/sendmail.pid`
This will cause sendmail to execute the command:
/usr/sbin/sendmail -bd -q1h
The original daemon exits, and the newly executed daemon replaces it.
Be aware that this works only if you run sendmail using a full pathname. If you use a relative
path, an attempt to restart sendmail withSIGHUP will fail, and the following warning
will be logged at LOG_ALERT:
could not exec bad command line here: reason
This is a very serious situation because it means that your original daemon has exited and
no new daemon ran to replace it.
Pages:
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911