public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: leio@hercules.dustbite.org
To: Norbert Kamenicky <noro@xmedia.sk>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Strange behavior of rc scripts
Date: Fri, 6 Jun 2003 17:20:14 +0300 (EEST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0306061713130.21795-100000@hercules.dustbite.org> (raw)
In-Reply-To: <3EE09A5C.7030800@xmedia.sk>

On Fri, 6 Jun 2003, Norbert Kamenicky wrote:

> On unixes it's quite common, that if some daemon started from
> init rc scripts fails, it's possible to re/start it paintless by  hand 
> again ...
> ( but not on Gentoo ? )

If a service is not running but the init system thinks it is, you just 
need to zap it, just as suggested in the initscripts helpfile (I believe 
it was /etc/init.d/<a initscript> help but I could remember wrong, not at 
home and forced to use MS Windows atm :( )

/etc/init.d/<initscript> zap

> When I switched from RH to Gentoo, the first thing
> I was worry about were rc init scripts, because I can
> only hardly to imagine something better then system 5 ones...
> let's try to convince me I am wrong :-)

Gentoo initscripts are just about perfect and work is in progress to make 
it even more perfect (if I recall correct then the initscript system is 
being developed to hold initscript dependencies in a tree so that multiple 
services can be started to increase boot-up time heavily)
If you cared to read the docs from gentoo.org you wouldn't ask about it.
http://www.gentoo.org/doc/en/rc-scripts.xml which is directly linked from 
the docs link on gentoo homepage.
Also such questions do NOT go to the gentoo-dev mailing list.

Mart Raudsepp


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-06-06 14:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-06 13:42 [gentoo-dev] Strange behavior of rc scripts Norbert Kamenicky
2003-06-06 14:20 ` leio [this message]
2003-06-06 14:46   ` Norbert Kamenicky

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.0306061713130.21795-100000@hercules.dustbite.org \
    --to=leio@hercules.dustbite.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=noro@xmedia.sk \
    /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