From: Mike Pomraning <mjp@pilcrow.madison.wi.us>
To: supervision@list.skarnet.org
Subject: Further chpst mods: alarm, documenting -r and -t, etc.
Date: Tue, 2 Oct 2012 00:03:58 -0500 [thread overview]
Message-ID: <CAPZFfA-QJH7Bb8NNFKjVjspB3hhhHUYwXumOqQDi+Mf8yHA7Xw@mail.gmail.com> (raw)
I've put my changes to chpst in a small fork of runit here:
https://github.com/pilcrow/runit . A diff against "vendor" branch
shows all changes.
Features:
- '-N' reopens '-012' to /dev/null, before any chroot, rather than closing
- '-2' no longer swallows errors
- '-A n' sets an alarm(2) for n seconds, or clears inherited alarm if n is zero
- rlimit options accept '=', just like softlimit(8)
- ./package/check (crudely) tests the new '-N' switch
Perhaps better than the above:
- man and html document previously undocumented '-r' and '-t' switches
- man and html clarify that rlimit opts are soft limits, silently
capped at the hard limit
-Mike
reply other threads:[~2012-10-02 5:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAPZFfA-QJH7Bb8NNFKjVjspB3hhhHUYwXumOqQDi+Mf8yHA7Xw@mail.gmail.com \
--to=mjp@pilcrow.madison.wi.us \
--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).