I updated the patch a bit, this one runs OK.

> > Hi,
> > The FAQ entry you give adds an upstart service for runit, which is
> > necessary since upstart currently doesn't read inittab.
> > 
> > But the FAQ is incorrect about starting that service. “telinit q” is
> > implemented as upstart's “initctl reload-configuration”, which
> > doesn't start newly added services.
> > The way to start the runsvdir service is to use /sbin/start
> > runsvdir.
> > 
> > I see there is no runit/upstart integration at all currently, which
> > is OK, and might be fixed by the current plan of making upstart more
> > sysv-compatible.
> > 
> > I suggest you update your FAQ to mention “/sbin/start SV” instead,
> > as well as the recent /etc/event.d/ -> /etc/init/ move.
> 
> Thanks.  I haven't dealt with upstart lately, can you confirm that
> this patch properly fixes the documentation?:

diff --git a/doc/useinit.html b/doc/useinit.html
index 58adec2..a5c2853 100644
--- a/doc/useinit.html
+++ b/doc/useinit.html
@@ -48,21 +48,22 @@ and tell <i>init</i> to re-read its configuration,
e.g.: <a name="upstart"><h2>Using with sysvinit and upstart</h2></a>
 If your system uses a sysvinit alike init scheme that utilizes upstart
 instead of inittab, and which has start and stop scripts located in
-<tt>/etc/event.d</tt>, do:
+<tt>/etc/init/</tt>, do:
 <pre>
- # cat >/etc/event.d/SV <<\EOT
- # for runit - manage /sbin/runsvdir-start
- start on runlevel-2
- start on runlevel-3
- start on runlevel-4
- start on runlevel-5
+ # cat >/etc/init/runsvdir.conf <<\EOT
+ # for runit - manage /usr/sbin/runsvdir-start
+ start on runlevel 2
+ start on runlevel 3
+ start on runlevel 4
+ start on runlevel 5
  stop on shutdown
- respawn /sbin/runsvdir-start
+ respawn
+ exec /usr/sbin/runsvdir-start
  EOT
 </pre>
-and tell init to re-read its configuration, e.g.:
+and tell init to start the new service, e.g.:
 <pre>
- # init q
+ # start runsvdir
 </pre>
 <hr>
 <a name="bsd"><h2>Using with *BSD init</h2></a>

-- 
Gabriel de Perthuis



--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to