On Sun, Feb 27, 2011 at 07:10:09PM +0100, Reindl Harald wrote:
> Thank you for your informations and very good documentation!
>
> Has anybody an eye to systemd/postfix because systemd will
> replace sysvinit/upstart in the upcoming Fedora 16 and
> so also in future RHEL-Versions and maybe replace
> upstart/sysvinit sooner or later in other distributions
> because the design of systemd seems to be really good
Postfix is not a simple daemon processing requests from a single socket.
The master.cf file specifies multiple services, some may be temporarily
disabled via "master_service_disable", ... On top of that there can
be multiple Postfix instances.
What this means is that Postfix needs to run when the system is started,
and stop when the system is stopped. Attempting to tie this to network
or file-system events is unwise except perhaps in the most trivial
deployments (null-client laptop), where Postfix may well be the wrong
choice of MTA. [ It is cute that Postfix code I contributed is included
on my MacBook, but I never use it, I use Apple's MUA, configured to send
to a real Postfix port 587 submission service. ]
Integration with systemd (which does appear better designed than upstart)
is I think easier than with upstart. Postfix can continue to be a classic
LSB init.d service. It looks no changes to Postfix are required to support
systemd.
--
Viktor.
