Re: Linux startup issue

Re: Linux startup issue

[Jonathan de Boyne Pollard]

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}").

Re: Linux startup issue

[Paul Jarc]

Jonathan de Boyne Pollard <J.deBoynePollard@Tesco.NET> wrote:
> 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.

More specifically:
- If the service is down to begin with, "svc -t" will have no effect;
  "svc -du" will bring the service up, with automatic restarting.
- If the service is running once from "svc -o", then "svc -t" will
  take it down and leave it down; "svc -du" will take it down and
  bring it back up, with automatic restarting; "svc -do" will take it
  down and bring it back up, without automatic restarting, just as it
  was originally.  (supervise publishes enough information in
  supervise/status to distinguish the "-o" state from the "-u" state,
  but svstat doesn't report it.)
- "svc -d" sends SIGTERM and SIGCONT, so if the service is stopped
  with SIGSTOP, it will be allowed to run again so it can exit.
  "svc -t" sends only SIGTERM, which is not sufficient to kill a
  stopped process, but it can be combined with "svc -c" for the same
  effect as "svc -d" (without turning off restarting).


paul

Re: Linux startup issue

[Stefan Karrmann]

Paul Jarc (Sat, Aug 14, 2004 at 02:58:26AM -0400):
> Jonathan de Boyne Pollard <J.deBoynePollard@Tesco.NET> wrote:
> > 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.
> 
> More specifically:
> - If the service is down to begin with, "svc -t" will have no effect;
>   "svc -du" will bring the service up, with automatic restarting.
> - If the service is running once from "svc -o", then "svc -t" will
>   take it down and leave it down; "svc -du" will take it down and
>   bring it back up, with automatic restarting; "svc -do" will take it
>   down and bring it back up, without automatic restarting, just as it
>   was originally.  (supervise publishes enough information in
>   supervise/status to distinguish the "-o" state from the "-u" state,
>   but svstat doesn't report it.)
> - "svc -d" sends SIGTERM and SIGCONT, so if the service is stopped
>   with SIGSTOP, it will be allowed to run again so it can exit.
>   "svc -t" sends only SIGTERM, which is not sufficient to kill a
>   stopped process, but it can be combined with "svc -c" for the same
>   effect as "svc -d" (without turning off restarting).

My 2 cent:

- Use svc -tcu if the service is up.
- Use svc -tco if the service is running once.

-- 
Stefan