Let's see if I got the gist of this thread: Fork & detach: the intended the default (although broken in 2.1.4) because most people expect it to work this way.
Fork & no-detach: parents stays connected to the tty so that failures are quickly detected by an appropriate wrapper script / init / whatever. Should be trivial to do, and makes a lot of sense. No-fork & no-detach (-n flag): required for inetd operation. Works. Aaron On Mon, 2006-03-06 at 22:54 +0100, Marc Dirix wrote: > I think if you want to start the process in your special > way, you could make an option for dbmail to not daemonize, and > let the others use it like they are used to. There are a lott good > daemons who have an console switch to not fork and kill tty. > > /Marc > > _______________________________________________ > Dbmail-dev mailing list > [email protected] > http://twister.fastxs.net/mailman/listinfo/dbmail-dev
