From: Dylan Carlson <absinthe@pobox.com>
To: vapier@gentoo.org, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Starting/stopping services
Date: Tue, 21 Jan 2003 10:39:45 -0500 [thread overview]
Message-ID: <200301211039.45740.absinthe@pobox.com> (raw)
In-Reply-To: <200301210409.59280.vapier@gentoo.org>
On Tuesday 21 January 2003 04:09 am, Mike Frysinger wrote:
> this allows for better control/checking via scripts and what not ...
>
> if theres an error/issue stopping a service, i want to know about it ...
> but if you dont care, just zap it ...
> -mike
>
> On Tuesday 21 January 2003 03:56, Matt Tucker wrote:
> > -- will <willg@bluesock.org> spake thusly:
> > > They can't be stopped because there's nothing to be stopped.
> > > However, zap should work.
> > >
> > > If you do "/sbin/runscript", then it'll tell you all about runscript
> > > stuff.
> >
> > Is there any particularly good reason that stop doesn't just do this
> > automatically?
I would like to have the ability to zap a service as "started". There are
some scenarios where a startup script will fire off many background
processes and might fail on one or two of them.
The script will be flagged as "stopped", but the background processes that
are running will keep running. So if there was way to set the script as
"started", you could do a normal stop to kill off whatever did manage to
start, instead of manually killing off processes.
Cheers,
Dylan Carlson [absinthe@pobox.com]
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-01-21 15:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-18 17:52 [gentoo-dev] Starting/stopping services Andy Arbon
2003-01-18 18:09 ` Caleb Shay
2003-01-18 18:09 ` Burton Samograd
2003-01-18 18:11 ` will
2003-01-21 8:56 ` Matt Tucker
2003-01-21 9:09 ` Mike Frysinger
2003-01-21 15:39 ` Dylan Carlson [this message]
2003-01-21 20:15 ` J Robert Ray
2003-01-21 21:15 ` Dylan Carlson
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=200301211039.45740.absinthe@pobox.com \
--to=absinthe@pobox.com \
--cc=gentoo-dev@gentoo.org \
--cc=vapier@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