From: Mark Francis <mark@canb2c.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] New USE flag 'daemontools' as an alternative to init.d
Date: Wed, 17 Sep 2003 17:00:37 +1000 [thread overview]
Message-ID: <3F680695.2060009@canb2c.com> (raw)
In-Reply-To: <20030911181811.GA2907@data.is>
I have created bugs 28938, 28940, 28941, 28943 and 28945 to add daemontools support
to the init scripts for samba, xinetd, fcron, cupsd and syslog-ng. Feel free to try
it and see what you think.
I discuss my approach in bug 28294. To summarise:
1. daemontools is not required but can optionally be used if available.
2. The daemontools service directory for each daemon is located in /var/daemontools
3. This method has flexibility in that a user can choose to start each daemon in
one of 3 different ways. The existing method (usually start-stop-daemon) in an init
script, supervise from an init script, or svscan by creating a link to /var/daemontools/$name
at /service/$name. Running supervise from the init script has the advantages of both
init dependancy support and daemon monitoring.
4. No daemontools USE flag is required using this method.
Mark
Hallgrimur H. Gunnarsson wrote:
>On 11.09.2003 Frederick Grim <fgrim@norby.dyndns.org> wrote:
>
>
>>#!/bin/sh
>>
>>exec /usr/bin/tcpserver 0 111 /sbin/portmap -d 2>&1
>>
>>with it's associated log/run script
>>
>>#!/bin/sh
>>exec /usr/bin/setuidgid nobody /usr/bin/multilog t s2500000
>>/var/log/supervise/portmap
>>
>>which bypasses these dependancies. I have found, using daemontools
>>that the system logger is only useful for a few broken daemons that
>>can't be configured to log to stdout.
>>
>>So this is sort of an important point. If runscripts are included
>>will the logging by default be to the stdout or to syslog?
>>
>>
>
>I think it should definitely be stdout by default, even if it were
>just to force that support into all packages who wish to provide
>daemontools support, so that you dont install a program that claims
>to support 'daemontools' but doesnt allow to use another logger than
>syslog.
>
>Perhaps we should come up with some method in which 'run' files
>are installed?
>
>Should we have a /etc/supervise/packagename or
>/etc/daemontools/packagename, or something like that?
>
>- hhg
>
>--
>gentoo-dev@gentoo.org mailing list
>
>
>
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-09-17 7:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 21:11 [gentoo-dev] New USE flag 'daemontools' as an alternative to init.d Hallgrimur H. Gunnarsson
2003-09-09 21:16 ` Matt Thrailkill
2003-09-09 21:43 ` Bryan D. Stine
2003-09-09 21:44 ` Hallgrimur H. Gunnarsson
2003-09-09 21:51 ` Hallgrimur H. Gunnarsson
2003-09-09 22:24 ` Bryan D. Stine
2003-09-10 9:33 ` Juan Jesus Prieto
2003-09-10 6:46 ` Martin Lesser
2003-09-11 13:57 ` Wes Chow
2003-09-11 16:00 ` Hallgrimur H. Gunnarsson
2003-09-11 13:53 ` Henti Smith
2003-09-11 16:13 ` Hallgrimur H. Gunnarsson
2003-09-11 16:28 ` Andrew Gaffney
2003-09-11 14:01 ` Henti Smith
2003-09-11 16:27 ` Wes Chow
2003-09-11 16:38 ` Hallgrimur H. Gunnarsson
2003-09-11 18:02 ` Frederick Grim
2003-09-11 18:16 ` Frederick Grim
2003-09-11 18:18 ` Hallgrimur H. Gunnarsson
[not found] ` <20030911183642.GC5824@norby.dyndns.org>
2003-09-11 18:46 ` [gentoo-dev] Re: gentoo-dev@gentoo.org Hallgrimur H. Gunnarsson
2003-09-17 7:00 ` Mark Francis [this message]
2003-09-17 14:38 ` [gentoo-dev] New USE flag 'daemontools' as an alternative to init.d Petre Rodan
2003-09-11 12:19 ` Petre Rodan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F680695.2060009@canb2c.com \
--to=mark@canb2c.com \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox