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-smarden-supervision@budge.apana.org.au>
Cc: supervision@list.skarnet.org
Subject: Re: /etc/runit/3 not executing correctly...
Date: Tue, 27 Jul 2004 14:42:59 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0407271431410.21937-100000@e-smith.charlieb.ott.istop.com> (raw)
In-Reply-To: <200407272026.35312.knoglen@tele2.fr>


On Tue, 27 Jul 2004, John Nielsen wrote:

> > I found out where the message comes from. It is generated by the util-linux
> > version of shutdown I am using. Its last action before it halts the
> > computer is to umount everything that is left.
> >
> > I then tried to reinstall the sysvinit version of shutdown and that worked
> > a lot better.
> >
> > So all of this seems to be caused by util-linux shutdown not wanting to
> > play nice with runit.

So don't use util-linux's shutdown :-)

> > I would really love to be abel to completely dump the sysvinit package. I
> > guess my case is a special one since I am not using a standart distro.
> 
> I feel lonely like this, replying to myself all the time. :-)
> 
> I solved the problem. Instead of trying to make the util-linux versions of the 
> files work, I wrote my own damn files!

/etc/runit/stopit, /etc/runit/reboot and /etc/runit/3 should do all.

> Actueally they are shell scripts calling init with different paramenters. They 
> appear to work like a charm. I allso got ctrl-alt-del to work as i want. This 
> is definetely starting to look like something.
> 
> I noticed a strange problem however. Every time i shut down, the getties dies 
> except for the getties that are logged in. I have to start the shutdown 
> script and then log out on that console.

I'd guess that is because getty is responding correctly to the TERM 
signal, but whatever you replace getty with (login, or a successor) does 
not.

> I know that I can specify a timeout on svwaitdown that kills the service when 
> the timeout has been reached, only this doesnt seem like a very clean 
> shutdown. Is it possible to shut down the session cleanly without killing it? 

Yes and no. All you can do is give the session leader a HUP or TERM
signal. You want it to respond appropriately to that signal, and tidy
everything up and then exit. But it could just ignore the signal, in which
case you need a bigger hammer (e.g. a QUIT signal, or -9).

> Im talking about something along the lines of what sysvinit does. Im guessing 
> something you would put in the /etc/runit/getty-*/finish script.

Those scripts won't necessarily be run when you want them to.


Charlie



  reply	other threads:[~2004-07-27 18:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-26 16:10 John Nielsen
2004-07-26 16:18 ` Laurent Bercot
2004-07-26 18:06   ` John Nielsen
2004-07-27 10:43     ` Gerrit Pape
2004-07-27 16:23       ` John Nielsen
2004-07-27 16:55         ` John Nielsen
2004-07-27 18:26           ` John Nielsen
2004-07-27 18:42             ` Charlie Brady [this message]
2004-07-28  8:25             ` Gerrit Pape
2004-07-28 17:03               ` John Nielsen

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.44.0407271431410.21937-100000@e-smith.charlieb.ott.istop.com \
    --to=charlieb-smarden-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).