public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: will <willg@bluesock.org>
To: Andy Arbon <gentoo@andrewarbon.co.uk>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Starting/stopping services
Date: Sat, 18 Jan 2003 12:11:40 -0600 (CST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0301181208001.31463-100000@www.bluesock.org> (raw)
In-Reply-To: <3E29946B.4000004@andrewarbon.co.uk>


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.

/will


On Sat, 18 Jan 2003, Andy Arbon wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hello,
> 
> I'd like to mention a problem that I see occasionally and see if anyone
> else considers it annoying enough to have fixed somehow.
> 
> The problem is that services can't be stopped (via /etc/init.d/* ) if
> the process they started has died since the init script started it.
> 
> Presumably the scripts try to terminate the process, find that it's not
> there anymore and exit with an error, but this means that there is no
> way (aside from starting a process with the correct name then letting
> the script kill it) to start the service again until the system
> restarts, which proves very annoying if you're doing anything which
> causes services to die frequently (in my case I'm playing with the
> lircd, which is a little flaky sometimes).
> 
> Is there anything that can be done about this? If the script tries to
> stop a service and finds the process has died then it probably should
> report an error, but I think it should also register that the service
> has stopped so that it can be restarted.
> 
> Cheers,
> 
> Andy
> 
> 
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.1 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iD8DBQE+KZRqX3TTUvZURBERAu1/AKCOJ34Hz/aeL/piAOd2lOgPJSnnhgCfcogr
> 0D28blwIFmGEHKU+SfRs6O4=
> =5djP
> -----END PGP SIGNATURE-----
> 
> 
> --
> gentoo-dev@gentoo.org mailing list
> 

-- 
whatever it is, you can find it at http://www.bluesock.org/~willg/
except Will--you can only see him in real life.



--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-01-18 18:16 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 [this message]
2003-01-21  8:56   ` Matt Tucker
2003-01-21  9:09     ` Mike Frysinger
2003-01-21 15:39       ` Dylan Carlson
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=Pine.LNX.4.44.0301181208001.31463-100000@www.bluesock.org \
    --to=willg@bluesock.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=gentoo@andrewarbon.co.uk \
    /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