supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Jonathan de Boyne Pollard <J.deBoynePollard@Tesco.NET>
Cc: supervision@list.skarnet.org
Subject: Re: Linux startup issue
Date: Fri, 13 Aug 2004 09:41:08 +0000	[thread overview]
Message-ID: <c1.01.2sP145$5AJ@J.de.Boyne.Pollard.localhost> (raw)
In-Reply-To: <Pine.LNX.4.61.0408121801310.23255@avion.km3t.org>

DP> I use the following script to start/restart DNS services:
DP> http://km3t.org/dns

1.  This will only be necessary if you have configured your services to 
initially be in the "down" state.
2.  "Restart" is better implemented as "svc -t" rather than as "svc 
-du", since the latter has the side-effect of changing the current state 
(to "up") whereas the former does not.

DP> Here is my /etc/inittab:
DP> http://km3t.org/inittab

The root cause of your problem is the fact that you have told "init" not 
to bring up "svscan" until _after_ all of your "rc[0-9]" scripts have 
been run.  Reconfigure so that "init" starts "svscan" _before_ your 
run-level scripts are invoked.

DP> Any ideas or help appreciated.

<URL:http://homepages.tesco.net./~J.deBoynePollard/Softwares/solaris-and-daemontools.html>
<URL:http://smarden.org/runit/runscripts.html>

The only jobs of a "run level" should be
* to change the ("up","down") states of a set of services,
and
* to (indirectly) trigger various one-time transition actions (e.g. by 
modifying "/etc/runit/{stopit,reboot}").



       reply	other threads:[~2004-08-13  9:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.61.0408121801310.23255@avion.km3t.org>
2004-08-13  9:41 ` Jonathan de Boyne Pollard [this message]
2004-08-14  6:58   ` Paul Jarc
2004-08-14 17:20     ` Stefan Karrmann

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='c1.01.2sP145$5AJ@J.de.Boyne.Pollard.localhost' \
    --to=j.deboynepollard@tesco.net \
    --cc=supervision@list.skarnet.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;
as well as URLs for NNTP newsgroup(s).