public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "William Hubbs" <williamh@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/openrc:master commit in: man/
Date: Wed, 27 May 2015 19:15:40 +0000 (UTC)	[thread overview]
Message-ID: <1432753785.bcb9c44e73ccf332c7c961a6f82520699c6e776d.williamh@OpenRC> (raw)

commit:     bcb9c44e73ccf332c7c961a6f82520699c6e776d
Author:     Mike Gilbert <floppym <AT> gentoo <DOT> org>
AuthorDate: Tue May 19 01:23:11 2015 +0000
Commit:     William Hubbs <williamh <AT> gentoo <DOT> org>
CommitDate: Wed May 27 19:09:45 2015 +0000
URL:        https://gitweb.gentoo.org/proj/openrc.git/commit/?id=bcb9c44e

man: Document the stopsig variable

This variable can be used to set the signal to send if the service is
using start-stop-daemon.

This fixes #56

 man/openrc-run.8 | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/man/openrc-run.8 b/man/openrc-run.8
index f08ad79..4637fd0 100644
--- a/man/openrc-run.8
+++ b/man/openrc-run.8
@@ -141,6 +141,8 @@ will chroot into this path before writing the pid file or starting the daemon.
 Pidfile to use for the above defined command.
 .It Ar name
 Display name used for the above defined command.
+.It Ar stopsig
+Signal to send when stopping the daemon.
 .It Ar retry
 Retry schedule to use when stopping the daemon. It can either be a
 timeout in seconds or multiple signal/timeout pairs (like SIGTERM/5).


             reply	other threads:[~2015-05-27 19:15 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-27 19:15 William Hubbs [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-05-15 22:11 [gentoo-commits] proj/openrc:master commit in: man/ William Hubbs
2018-05-07 23:21 William Hubbs
2018-03-12 23:23 William Hubbs
2018-03-12 23:23 William Hubbs
2018-02-10 20:52 William Hubbs
2018-02-10 20:52 William Hubbs
2017-11-30 22:04 William Hubbs
2017-11-29 21:12 William Hubbs
2017-10-12 23:55 William Hubbs
2017-09-22 22:25 William Hubbs
2017-07-26 16:32 William Hubbs
2017-07-25 18:57 William Hubbs
2017-07-08 16:55 William Hubbs
2017-07-08 16:55 William Hubbs
2017-06-07 16:34 William Hubbs
2017-05-12  3:01 William Hubbs
2017-04-14 16:11 William Hubbs
2016-12-05 18:27 William Hubbs
2016-12-02 16:58 William Hubbs
2016-09-22 15:30 William Hubbs
2016-09-21 18:35 William Hubbs
2016-09-13 19:09 William Hubbs
2016-06-23 22:55 William Hubbs
2015-12-03 23:45 William Hubbs
2015-05-11 20:39 William Hubbs
2014-11-22 18:39 William Hubbs
2014-09-19 23:00 William Hubbs
2014-07-13 16:25 William Hubbs
2014-07-13 16:25 William Hubbs
2014-07-11 21:41 William Hubbs
2014-06-21  7:05 William Hubbs
2014-01-08 19:27 William Hubbs
2013-08-24 17:05 William Hubbs
2013-08-15 15:22 William Hubbs
2013-08-13 17:22 William Hubbs
2013-03-20 20:45 William Hubbs
2012-10-22  0:53 William Hubbs
2012-10-16 19:29 Christian Ruppert
2012-10-16 19:00 Christian Ruppert
2012-09-25 17:09 William Hubbs
2012-09-24  0:37 William Hubbs
2012-03-24 17:40 William Hubbs
2012-02-19 19:18 William Hubbs
2012-02-19 18:54 William Hubbs
2011-12-31  4:25 William Hubbs
2011-12-31  4:25 William Hubbs
2011-12-31  2:44 Christian Ruppert
2011-12-30 16:41 William Hubbs
2011-12-30 15:03 Christian Ruppert
2011-04-08 19:10 William Hubbs

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=1432753785.bcb9c44e73ccf332c7c961a6f82520699c6e776d.williamh@OpenRC \
    --to=williamh@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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