aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorClayton Craft <clayton@craftyguy.net>2020-12-04 17:23:18 -0800
committerLuca Barbato <luca.barbato@gmail.com>2020-12-20 13:54:33 +0100
commit7019bfad3b4cf6eff31d967f6f4e0960f67858fb (patch)
tree65993fcac421aabe596a608527a6bb005471b4f6
parent8346c985d598385e760375a8adf69c986bb4a350 (diff)
user-guide: clarify note for Runlevels/rc-update usage
I found the original note a little confusing, since using rc-update will add it to a runlevel so it *is* auto-started when the system reaches that runlevel again, but I don't think that was the intended meaning of 'auto-start', so hopefully this makes it a little more clear.
-rw-r--r--user-guide.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/user-guide.md b/user-guide.md
index 275578e1..01b3add3 100644
--- a/user-guide.md
+++ b/user-guide.md
@@ -85,8 +85,8 @@ runlevel; this will start and stop services as needed.
Managing runlevels is usually done through the `rc-update` helper, but could of
course be done by hand if desired.
e.g. `rc-update add nginx default` - add nginx to the default runlevel
-Note: This will not auto-start nginx! You'd still have to trigger `rc` or run
-the service script by hand.
+Note: `rc-update` will not start nginx! You'd still have to trigger `rc`, or run
+the service script by hand, or start it with `rc-service nginx start`.
FIXME: Document stacked runlevels