supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Radek Podgorny <radek@podgorny.cz>
To: supervision@list.skarnet.org
Subject: Re: runit-1.9.0 available
Date: Fri, 16 May 2008 15:37:15 +0200	[thread overview]
Message-ID: <482D8E0B.6070901@podgorny.cz> (raw)
In-Reply-To: <g0k05j$394$1@ger.gmane.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

/me likes this idea, too...

Radek P.


Robin Bowes wrote:
| Zachary Kotlarek wrote:
|
|>> I've built netbooting/embedded systems where /etc was mounted
|>> read-only. Putting the run, check, supervise and finish scripts there
|>> makes sense -- but it would be nice if the supervise directories
|>> could be split out and stored elsewhere (presumably on tmpfs) in such
|>> environments.
|>
|> I do that exactly -- /, including /etc, is read-only on most of my
|> systems. I put scripts in /etc/supervise so they hit the configuration
|> management, and symlink the supervise directory to
|> /var/tmp/run/whatever so it can be read/write.
|
| That makes sense to me.
|
| What would make more sense is being able to specify that the supervise
| directory should be created in some location other than the service
| directory, e.g. /var/run/service_name.
|
| R.
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkgtjgsACgkQ7mej6pjlbYRaYACdFcp8LMNYIocJxbO9ouRViW8e
LIsAoKw2luyluv+iJQPtvl7DMar8czFE
=lyiI
-----END PGP SIGNATURE-----


  reply	other threads:[~2008-05-16 13:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-13  9:28 Gerrit Pape
2008-05-13 10:20 ` Robin Bowes
2008-05-13 10:48   ` Gerrit Pape
2008-05-14 23:11     ` George Georgalis
2008-05-15 17:10       ` Charles Duffy
2008-05-16  1:25         ` Zachary Kotlarek
2008-05-16 12:55           ` Robin Bowes
2008-05-16 13:37             ` Radek Podgorny [this message]
2008-05-16 15:07         ` Charles Duffy

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=482D8E0B.6070901@podgorny.cz \
    --to=radek@podgorny.cz \
    --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).