On Tue, Feb 06, 2001 at 05:16:36PM -0500, Peter Brezny wrote:
> our new qmail install is started simply by
>
> exec env - PATH="/var/qmail/bin:$PATH" \
> qmail-start ./Maildir splogger qmail&
>
> however I've noticed a lot of people using daemontools and supervise.
>
> What are the primary advantages of using supervise?
My personal thoughts:
1. multilog. multilog uses a lot less overhead than syslog, and does
not listen on the network, and so is not vulnerable to remote DoS or
exploit. It's self-rotating (configurable), and uses a super-accurate
timestamp (although the timestamp is not _that_ relevant to me
personally).
2. Unification with other djb-ware, especially djbdns. Personally, I'd
just love it if sshd could log to STDOUT, and that way most of my hosts
would use supervise for _all_ the important processes. ;)
3. Simple process control. Downing all supervised processes is as simple
as 'svc -d /service/*/log ; svc -d /service/*'. Gotta like that.
>
> Our mail server probably handles less than 2000 messges a day is it
> something I really need to do?
Need? No. But well worth it IMHO.
>
> Is there a good document that points to how to correctly configure supervise
> to start/run/manage qmail?
http://www.lifewithqmail.org/
Just snag and modify the /var/qmail/supervise directory structure and
'run' scripts.
>
> Thanks for your help.
You're welcome. ;)
>
> Peter Brezny
> SysAdmin Services Inc.
>
--
Greg White
Those who make peaceful revolution impossible will make violent
revolution inevitable.
-- John F. Kennedy
