public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matt Thrailkill <xwred1@xwredwing.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] New USE flag 'daemontools' as an alternative to init.d
Date: Tue, 9 Sep 2003 14:16:51 -0700	[thread overview]
Message-ID: <20030909141651.3cfe58a4.xwred1@xwredwing.net> (raw)
In-Reply-To: <20030909211112.GA20604@data.is>

Is this effectively a new system of init-scripts?

If so.. I think it'd be cool to write some bsd-style init-scripts to add
to the variety.

On Tue, 9 Sep 2003 21:11:12 +0000
"Hallgrimur H. Gunnarsson" <hhg@data.is> wrote:

> Hello friends !
> 
> I'd like to propose a new USE flag.
> 
> On my systems I've added a 'daemontools' USE flag
> as an alternative to the current init.d for
> service management. To be a true metadistribution,
> it doesn't seem fair to let init.d have a monopoly
> on providing service management for packages.
> 
> For those who haven't heard of it before, daemontools
> is a process supervisor that can manage services.
> For more information see http://cr.yp.to/daemontools.html
> 
> Integration of this functionality into ebuilds is in
> most cases very trivial. Packages that wish to
> provide daemontools USE flag support provide
> a 'run' file, that is copied to a service directory,
> /etc/daemontools/servicename, or something in that
> direction.  We could even have some automated facility
> for preparing service directories.
> 
> People can then choose what to use for running a particular
> service, /etc/init.d or linking the service directory into
> /service if the package provides daemontools support.
> 
> I've opened a bug for this (#28294), so what do people
> think of this?
> 
> -- hhg
> 
> 
> --
> gentoo-dev@gentoo.org mailing list
> 
> 

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-09-09 21:34 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 [this message]
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             ` [gentoo-dev] New USE flag 'daemontools' as an alternative to init.d Mark Francis
2003-09-17 14:38               ` 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=20030909141651.3cfe58a4.xwred1@xwredwing.net \
    --to=xwred1@xwredwing.net \
    --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