From ed9895aaa048e1f21524d4cbbb3e5257f037f706 Mon Sep 17 00:00:00 2001 From: Jacob Vosmaer Date: Mon, 7 Apr 2014 17:17:45 +0200 Subject: [PATCH] More explanation about runsvdir and gitlab-ctl --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 7c05a77..aa333a4 100644 --- a/README.md +++ b/README.md @@ -40,9 +40,9 @@ For update instructions, see [the update guide](doc/update.md). After omnibus-gitlab is installed and configured, your server will have a Runit service directory (`runsvdir`) process running that gets started at boot via -`/etc/inittab` or the `gitlab-runsvdir` Upstart resource. Do not touch the -`runsvdir` process; to manage GitLab processes you should use `gitlab-ctl` -instead. +`/etc/inittab` or the `/etc/init/gitlab-runsvdir.conf` Upstart resource. You +should not have to deal with the `runsvdir` process directly; you can use the +`gitlab-ctl` front-end instead. You can start, stop or restart GitLab and all of its components with the following commands. -- libgit2 0.21.2