The ControlSocketName option enables this type of
controlling interface. It is declared like this:
O ControlSocketName=path ?†? configuration file (V8.10 and later)
-OControlSocketName=path ?†? command line (V8.10 and later)
define(`confCONTROL_SOCKET_NAME??, path) ?†? mc configuration (V8.10 and later)
This is the Title of the Book, eMatter Edition
Copyright ?© 2007 O??™Reilly & Associates, Inc. All rights reserved.
24.9 Alphabetized Options | 991
Here, the argument path, of type string, is the full pathname of the Unix named socket. The
file named by path need not exist. If it exists, sendmail will remove it and create a new
named socket. As a consequence, you should avoid accidently declaring path withan
existing file. The file will be silently removed when sendmail starts.
The path needs to be secure. That is, every component of it should be owned by, and writable
only by, root or the trusted user specified in the TrustedUser option (?§24.9.122 on
page 1112). Because this interface can be used to shut down the sendmail daemon, the
socket requires extra protection. On some operating systems (suchas withSolaris and pre-
4.4 BSD kernels), it is not enough to make the socket mode 0600. You should also place it
in a directory that is root-owned and of mode 0700. On suchoperating systems, if you put
it in a directory that is world-searchable, anyone on the same machine will be able to shut
down the daemon.
Pages:
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756