Download as
Browse Code »

Commit ed9895aaa048e1f21524d4cbbb3e5257f037f706

Authored by Jacob Vosmaer
1 parent c6aed5d7
Exists in master and in 13 other branches 6-8-stable, 6-8-stable-ee, 6-9-stable, 6-9-stable-ee, 7-0-stable, 7-0-stable-ee, 7-0-stable-spb, 7-1-stable, 7-1-stable-ee, 7-2-stable, 7-2-stable-ee, branch_test, nginx_ssl_tweaks

More explanation about runsvdir and gitlab-ctl

Showing 1 changed file with 3 additions and 3 deletions   Show diff stats
@@ -40,9 +40,9 @@ For update instructions, see [the update guide](doc/update.md). @@ -40,9 +40,9 @@ For update instructions, see [the update guide](doc/update.md).
40 40
41 After omnibus-gitlab is installed and configured, your server will have a Runit 41 After omnibus-gitlab is installed and configured, your server will have a Runit
42 service directory (`runsvdir`) process running that gets started at boot via 42 service directory (`runsvdir`) process running that gets started at boot via
43 -`/etc/inittab` or the `gitlab-runsvdir` Upstart resource. Do not touch the  
44 -`runsvdir` process; to manage GitLab processes you should use `gitlab-ctl`  
45 -instead. 43 +`/etc/inittab` or the `/etc/init/gitlab-runsvdir.conf` Upstart resource. You
  44 +should not have to deal with the `runsvdir` process directly; you can use the
  45 +`gitlab-ctl` front-end instead.
46 46
47 You can start, stop or restart GitLab and all of its components with the 47 You can start, stop or restart GitLab and all of its components with the
48 following commands. 48 following commands.