First, you need
to kill all the competing sendmail queue-processing daemons. There are a wide number
of ways to do this. The most common is to use ps(1) to gather PID numbers and
then kill each queue-processing daemon individually. No matter how you kill the
This is the Title of the Book, eMatter Edition
Copyright ?© 2007 O??™Reilly & Associates, Inc. All rights reserved.
408 | Chapter 11: Manage the Queue
queue-processing daemons, be sure to kill them all. If you don??™t, you might find the
problem surfacing again before you have had a chance to fix it.
The best way to flush a full queue is with a command line something like this:
# /usr/sbin/sendmail -OQueueSortOrder=filename -q10m -d99.100
# /usr/sbin/sendmail -OQueueSortOrder=random -q10m -d99.100 ?†? V8.12 and later
# /usr/sbin/sendmail -OQueueSortOrder=none -q10m -d99.100 ?†? V8.13 and later
Here, the -d99.100 tells sendmail to run in the foreground (so that you can kill it easily
when done). The -q10m causes a queue-processing daemon to be launched once
each10 minutes (just like before). You need this because one daemon can seem to
hang when delivering mail to a slow host. By running parallel daemons, you avoid
this pitfall.
Sorting by filename or random (?§11.7 on page 426) or none (V8.13 and later) causes
sendmail to skip the opening and reading of each queued message.
Pages:
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735