supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Adam Megacz <megacz@cs.berkeley.edu>
Cc: rra@stanford.edu, pape@smarden.org
Subject: contrib OpenAFS server script for runit  [Was: "sv down foo" => kill -SIGQUIT?]
Date: Sat, 03 Jun 2006 12:21:08 -0700	[thread overview]
Message-ID: <x3d5dqf3kr.fsf_-_@nowhere.com> (raw)
In-Reply-To: <20060603120409.GA24322@home.power>


Alex Efros <powerman@powerman.asdfGroup.com> writes:
>> Is there any way to tell runit that this process wants to be sent a
>> SIGQUIT rather than SIGTERM?  I know about "sv quit foo", but I'm
>> worried I'll accidentally type "sv down foo".
>
> Check runsv manual page, 'CUSTOMIZE CONTROL' section.

Perfect!  Thanks!  I'd like to contribute the following configuration
to handle the OpenAFS server suite (openafs.org)

/var/service/afs-server/run

  #!/bin/bash
  exec /usr/sbin/bosserver -nofork

/var/service/afs-server/control/t

  #!/bin/bash
  sv quit afs-server

Bosserver really needs to be sent SIGQUIT; if you sent it SIGTERM it
will die but leave its child processes running (orphaned), at which
point they're difficult to easily shut down cleanly.

You might want to consider adding this here in case other people don't
know about the SIGQUIT thing (it took me a while to figure it out).

  http://smarden.org/runit/runscripts.html

Thanks again; runit is great!

  - a


-- 
PGP/GPG: 5C9F F366 C9CF 2145 E770  B1B8 EFB1 462D A146 C380



      reply	other threads:[~2006-06-03 19:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-03  6:42 "sv down foo" => kill -SIGQUIT? Adam Megacz
2006-06-03 12:04 ` Alex Efros
2006-06-03 19:21   ` Adam Megacz [this message]

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=x3d5dqf3kr.fsf_-_@nowhere.com \
    --to=megacz@cs.berkeley.edu \
    --cc=pape@smarden.org \
    --cc=rra@stanford.edu \
    /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).