??? If a persistent queue runner fails and exits, the controlling process will launch a
new persistent queue runner.
If a persistent queue runner core-dumps, the following will be logged and that queue
runner will not be restarted:
persistent queue runner=number core dumped, signal=signal
If a persistent queue runner exits because of a caught signal, the following is logged
and that queue runner is restarted:
persistent queue runner=number died, signal=signal
If a persistent queue runner is restarted because of a SIGHUP, the following is
logged:
restart queue runner=number due to signal signal
If the -dno_persistent_restart debugging command-line switchis specified, a failed
persistent queue runner will not be restarted, and the following error will be logged:
persistent queue runner=number, exited
A persistent queue runner will not be restarted if it has already been restarted 10
times. Instead, the following error will be logged and that persistent queue runner
marked as bad:
ERROR: persistent queue runner=number restarted too many times, queue runner lost
If this happens, examine your logs. Some nonmail-related process might be signaling
your persistent queue runners, or you might have bad memory, or you might have
made a mistake when building sendmail and should rebuild it, or you might have a
junior system administrator who does not know how to correctly restart sendmail.
Pages:
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784