From: "William Hubbs" <williamh@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/openrc:master commit in: etc/
Date: Tue, 30 Oct 2012 16:17:29 +0000 (UTC) [thread overview]
Message-ID: <1351613540.eff07c48b7a2266a4c82a202960856b4f39936d0.WilliamH@OpenRC> (raw)
commit: eff07c48b7a2266a4c82a202960856b4f39936d0
Author: William Hubbs <w.d.hubbs <AT> gmail <DOT> com>
AuthorDate: Tue Oct 30 16:12:20 2012 +0000
Commit: William Hubbs <williamh <AT> gentoo <DOT> org>
CommitDate: Tue Oct 30 16:12:20 2012 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/openrc.git;a=commit;h=eff07c48
Expand the documentation for service configuration variables
The original documentation for these variables did not give an example
of what to do if the service had a name that had illegal characters in
it, so this commit adds an example. There was no bug report; this was
suggested by Tobias Klausmann.
---
etc/rc.conf.in | 11 +++++++++++
1 files changed, 11 insertions(+), 0 deletions(-)
diff --git a/etc/rc.conf.in b/etc/rc.conf.in
index 2dad333..e49a410 100644
--- a/etc/rc.conf.in
+++ b/etc/rc.conf.in
@@ -94,6 +94,10 @@
# These variables are documented here, but should be configured in
# /etc/conf.d/foo for service foo and NOT enabled here unless you
# really want them to work on a global basis.
+# If your service has characters in its name which are not legal in
+# shell variable names and you configure the variables for it in this
+# file, those characters should be replaced with underscores in the
+# variable names as shown below.
# Some daemons are started and stopped via start-stop-daemon.
# We can set some things on a per service basis, like the nicelevel.
@@ -116,6 +120,13 @@
#rc_foo_need="openvpn"
#rc_foo_after="clock"
+# Below is an example for service foo-bar. Note that the '-' is illegal
+# in a shell variable name, so we convert it to an underscore.
+# example for service foo-bar.
+#rc_foo_bar_config="/etc/foo-bar"
+#rc_foo_bar_need="openvpn"
+#rc_foo_bar_after="clock"
+
# You can also remove dependencies.
# This is mainly used for saying which servies do NOT provide net.
#rc_net_tap0_provide="!net"
next reply other threads:[~2012-10-30 16:17 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 16:17 William Hubbs [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-12-15 23:56 [gentoo-commits] proj/openrc:master commit in: etc/ William Hubbs
2016-09-28 0:40 William Hubbs
2016-07-20 21:44 William Hubbs
2016-07-20 21:44 William Hubbs
2015-12-02 17:12 William Hubbs
2015-10-29 16:36 William Hubbs
2015-05-22 14:57 William Hubbs
2015-05-08 17:33 William Hubbs
2014-12-08 1:07 William Hubbs
2014-08-11 18:18 William Hubbs
2014-08-22 19:10 ` William Hubbs
2014-03-15 3:19 William Hubbs
2014-03-09 20:39 William Hubbs
2013-12-08 19:45 William Hubbs
2013-03-12 19:18 William Hubbs
2013-02-17 17:09 William Hubbs
2013-02-16 22:12 William Hubbs
2012-12-04 0:24 William Hubbs
2012-02-13 18:00 William Hubbs
2012-01-25 18:40 Christian Ruppert
2012-01-06 4:36 William Hubbs
2011-11-26 23:47 William Hubbs
2011-07-06 23:40 William Hubbs
2011-07-05 22:52 Christian Ruppert
2011-04-18 20:22 William Hubbs
2011-03-22 4:05 William Hubbs
2011-03-15 3:11 William Hubbs
2011-03-05 6:13 William Hubbs
2011-03-03 21:07 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=1351613540.eff07c48b7a2266a4c82a202960856b4f39936d0.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