From: Martin Schlemmer <azarah@gentoo.org>
To: Paul de Vrieze <pauldv@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] strange gentoo shutdown sequence
Date: Wed, 05 May 2004 20:11:05 +0200 [thread overview]
Message-ID: <1083780663.18004.22.camel@nosferatu.lan> (raw)
In-Reply-To: <200405031105.47155.pauldv@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1414 bytes --]
On Mon, 2004-05-03 at 11:05, Paul de Vrieze wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Monday 03 May 2004 10:50, Allen D Parker wrote:
> > We can actually probably do this in bash fairly simply (although
> > unless each service is started in sequence or in a seperate
> > shellspace, it might be a problem) parallel start + bash variables =
> > nastiness.
> >
> > for each initscript SVCNAME="apache2"
> > then in the actual runscript, something like this would do just fine
> > (imho) for 99% of what would need to be supported:
> >
> > SVCHOME=`whereis ${SVCNAME} | cut -d " " -f 2`
> > if ${SVCNAME} != `ps aux | grep ${SVCHOME}`; then
> > /etc/init.d/${SVCNAME} zap &&
> > /etc/init.d/${SVCNAME} start
> > else
> > SVC_STATUS="alive"
> > fi
>
> I was more thinking of providing an extra function (say "status()") that
> would have a positive result if the service is actually running and a
> negative result if it is not. The handler script/program should then be
> able to handle this function.
>
There is one that can be overridden. Also have a look at
/lib/rcscripts/sh/rc-daemon.sh - yeah, its crude, its very alpha (did
it in a night some months back), but it was supposed to be generic
daemon handling, with checking of pid, etc.
--
Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-05-05 18:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-02 17:32 [gentoo-dev] strange gentoo shutdown sequence William Hubbs
2004-05-03 5:10 ` John Nilsson
2004-05-03 6:15 ` Olivier Crête
2004-05-03 6:46 ` John Nilsson
2004-05-03 17:22 ` Grant Goodyear
2004-05-03 8:30 ` Paul de Vrieze
2004-05-03 8:50 ` Allen D Parker
2004-05-03 9:05 ` Paul de Vrieze
2004-05-05 18:11 ` Martin Schlemmer [this message]
2004-05-03 16:24 ` splite-gentoo
2004-05-04 15:13 ` [gentoo-dev] " Sven Köhler
2004-05-04 15:33 ` splite-gentoo
2004-05-04 16:00 ` Sven Köhler
2004-05-04 16:30 ` Jon Portnoy
2004-05-04 15:16 ` Sven Köhler
2004-05-04 15:37 ` splite-gentoo
2004-05-04 15:59 ` Sven Köhler
2004-05-04 16:25 ` splite-gentoo
2004-05-07 16:33 ` Chris Gianelloni
2004-05-07 17:53 ` splite-gentoo
2004-05-04 16:28 ` Daniel Drake
-- strict thread matches above, loose matches on Subject: below --
2004-05-02 11:40 [gentoo-dev] " Sven Köhler
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=1083780663.18004.22.camel@nosferatu.lan \
--to=azarah@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=pauldv@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