Zitat von Wietse Venema <wie...@porcupine.org>:
lst_ho...@kwsoft.de:The "problem" is more of that distribution like Ubuntu and Redhat are moving to "upstart" for boot and starting services/daemons. The main difference for the started services is that upstart need the program to *not* daemonize or terminate itself because status is checked directly to do respawn and other things if necessary and not by monitoring a PID like it was with sys-v. So basically to get Postfix upstart compatibel a "postfix-start-stop" helper would be needed which is always running and only does dispatching of start/stop requests to the master(s) according to Postfix needs.The problem with this approach is that Postfix is not one program, like named, apache, etc., and that simply starting one master daemon is insufficient as it skips all the start-up repair and sanity checks.
That's why i said it may be useful to have a simple "dispatcher/wrapper" which only is started to call "postfix start" and keeps running to keep upstart happy and calls "postfix stop/restart" when advised to do so by upstart. With this the supported way of starting/stopping is possible *and* upstart could be used without problems. The only problem to solve is the non-terminating behaviour required by upstart, all other startup work can be done as usual behind the scene.
Regards Andreas
smime.p7s
Description: S/MIME Cryptographic Signature
