supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Charlie Brady <charlieb-supervision@budge.apana.org.au>
To: Amrish Purohit <amrish.purohit@elitecore.com>
Cc: supervision@list.skarnet.org
Subject: Re: endless loop at stage 2 of runit of run scripts of each service directories.
Date: Mon, 11 Aug 2008 10:13:37 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0808111008250.25302@e-smith.charlieb.ott.istop.com> (raw)
In-Reply-To: <489FDBFF.4020206@elitecore.com>


On Mon, 11 Aug 2008, Amrish Purohit wrote:

> here is the format of run script
> ---------------------------------------
> #!/bin/bash
> exec /etc/rc.d/init.d/cpuspeed start

Doing that will always get you into trouble. init.d scripts are always 
designed to terminate quickly. That's exactly the opposite of what you 
want. Any program which you exec from a supervise run script is expected 
to keep running until you send it a signal asking for it to stop.

You will need to look through /etc/rc.d/init.d/cpuspeed and find out what 
commands it calls, and find a way to call the same command in a way where 
the command will not terminate (e.g. don't run it in the background, or 
run it with an argument which tells it to run in the foreground).

[Try:

exec /usr/sbin/cpuspeed

Or just use a symlink to /usr/sbin/cpuspeed as your /service/cpuspeed/run.
]



  reply	other threads:[~2008-08-11 14:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-11  6:28 Amrish Purohit
2008-08-11 14:13 ` Charlie Brady [this message]
2008-08-12  5:32   ` Amrish Purohit
2008-08-12 13:01     ` Charlie Brady

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.64.0808111008250.25302@e-smith.charlieb.ott.istop.com \
    --to=charlieb-supervision@budge.apana.org.au \
    --cc=amrish.purohit@elitecore.com \
    --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).