Template Version: @(#)sac_nextcase %I% %G% SMI
This information is Copyright 2009 Sun Microsystems
1. Introduction
1.1. Project/Component Working Name:
sendmail split-instance
1.2. Name of Document Author/Supplier:
Author: John Beck
1.3 Date of This Document:
14 January, 2009
4. Technical Description
I am self-sponsoring this case, which I believe is sufficiently obvious to
qualify for automatic approval; if anyone objects, I will upgrade it to a
fast-track. The interfaces are Committed and the release binding is Patch.
* Previous related cases
* PSARC 2001/812 sendmail 8.12
* PSARC 2002/547 Greenline
* PSARC 2008/042 automated building of sendmail configuration files
* Problem
Since version 8.12 (introduced in Solaris 9), sendmail has had two long-
running processes: the traditional daemon, and a client queue runner.
Since sendmail comes from outside Sun, it is not contract-aware, which
has led to occasional problems of the daemon dumping core and SMF not
restarting. This is because the client queue runner was still going and
thus the contract was not empty, so SMF would not know to restart it.
* Solution
Split the sendmail instance of the svc:/network/smtp service into two,
leaving the existing sendmail instance for the daemon, and adding a new
sendmail-client instance for the client queue runner. Man pages for
sendmail(1m) and sendmail(4) (old, new and diff'd) are available in the
case materials directory.
* Issues
* SBD
The sendmail instance will continued to be governed by its property
config/local_only as to whether it accepts connections only on
loopback addresses or from any IP address. As the sendmail-client
instance does not result in any open ports, and its process is
enabled by default currently, it will also be enabled by default.
* RBAC
The sendmail-client instance will use the same authorization value
(solaris.smf.manage.sendmail) as the sendmail instance.
* Automated config-file building
PSARC 2008/042 introduced the property config/path_to_submit_mc
for the sendmail instance. This property will now migrate to the
sendmail-client instance with the same semantics. Note that this
feature, though it has Patch release binding, has not yet been back-
ported, so this migration does not present any compatibility issues.
6. Resources and Schedule
6.4. Steering Committee requested information
6.4.1. Consolidation C-team Name:
ON
6.5. ARC review type: Automatic
6.6. ARC Exposure: open
