From: Charlie Brady <charlieb-supervision@budge.apana.org.au>
Cc: supervision@list.skarnet.org
Subject: Re: run scripts
Date: Mon, 17 Oct 2005 20:22:58 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.61.0510171939370.3848@e-smith.charlieb.ott.istop.com> (raw)
In-Reply-To: <43458F4B.5050903@zilli.gulinuxsul.org>
On Thu, 6 Oct 2005, Daniel Zilli wrote:
> I'm start working with runit and found it great. I would like to migrate
> all my rc.d scripts (slackware 10.2) to runit scheme. Some scripts are
> easy other hard to migrate. I would like some advise. What do I need
> consider when writing runit scripts ?
What's critically important is that the program must keep running, and
must not "put itself into the background" or "daemonize itself".
What's also important is that the TERM signal will actually cause the
process to shut down. A few badly behaved programs don't do that - mysql
in particular.
It's common practice to have programs log to stderr rather than via
syslog.
next prev parent reply other threads:[~2005-10-18 0:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-06 20:55 Daniel Zilli
2005-10-18 0:22 ` Charlie Brady [this message]
2005-10-18 9:27 ` TheOldFellow
2008-07-04 15:22 Run scripts Gilles Sadowski
2008-07-04 15:28 ` Mike Buland
2008-07-04 16:38 ` Gilles Sadowski
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.61.0510171939370.3848@e-smith.charlieb.ott.istop.com \
--to=charlieb-supervision@budge.apana.org.au \
--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).