summary refs log tree commit diff
path: root/doc/useinit.html
blob: 2623248b7f99bde606e0563a0e962e4233a4faf9 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
<html>
<head>
<title>runit - use with traditional init</title>
</head>
<body>
<a href="http://smarden.org/pape/">G. Pape</a><br>
<a href="index.html">runit</a><br>
<hr>
<h1>runit - use with traditional init</h1>
<hr>
It's possible to use <i>runit</i>'s service supervision without replacing
the <i>init</i> scheme of the system.
Simply run the <i>stage 2</i> of <i>runit</i> as a service with your
current <i>init</i>.
<p>
Normally this is done by either adding an entry for
<tt>/sbin/runsvdir-start</tt> to <tt>/etc/inittab</tt>, or by adding
<tt>/sbin/runsvdir-start</tt> as command to </tt>/etc/rc.local</tt>, or by
adding <tt>/sbin/runsvdir-start</tt> to the system's <tt>StartupItems</tt>.
<p>
In any case, you first need to copy the <i>stage 2</i> script to
<tt>/sbin/runsvdir-start</tt>, and create the services directory
<tt>/var/service/</tt>:
<pre>
 # install -m0750 /package/admin/runit/etc/2 /sbin/runsvdir-start
 # mkdir -p /var/service
</pre>
<hr>
<a href="#sysv">How to use with sysvinit and inittab</a><br>
<a href="#upstart">How to use with sysvinit and upstart</a><br>
<a href="#bsd">How to use with *BSD init</a><br>
<a href="#macosx">How to use with MacOSX init</a>
<hr>
<a name="sysv"><h2>Using with sysvinit and inittab</h2></a>
If your system uses a sysvinit alike init scheme with a <tt>/etc/inittab</tt>
file, do:
<pre>
 # cat &gt;&gt;/etc/inittab &lt;&lt;EOT
 SV:123456:respawn:/sbin/runsvdir-start
 EOT
</pre>
and tell <i>init</i> to re-read its configuration, e.g.:
<pre>
 # init q
</pre>
<hr>
<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:
<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
 stop on shutdown
 respawn /sbin/runsvdir-start
 EOT
</pre>
and tell init to re-read its configuration, e.g.:
<pre>
 # init q
</pre>
<hr>
<a name="bsd"><h2>Using with *BSD init</h2></a>
If your system uses a BSD alike init scheme with a <tt>/etc/rc.local</tt>
script, do:
<pre>
 # cat &gt;&gt;/etc/rc.local &lt;&lt;EOT
 csh -cf '/sbin/runsvdir-start &amp;'
 EOT
</pre>
and reboot your system.
<hr>
<a name="macosx"><h2>Using with MacOSX init</h2></a>
On MacOSX 10.2 create an entry for <i>runit</i> in
<tt>/System/Library/StartupItems/</tt>:
<pre>
 # cd /System/Library/StartupItems
 # mkdir -p runit
 # cp -p /package/admin/runit/etc/macosx/StartupItems/* runit/
</pre>
and reboot your system.
<p>
On MacOSX 10.4 create an entry for <i>runit</i> in
<tt>/Library/LaunchDaemons/</tt>, and tell <i>launchd</i> to start the new 
service:
<pre>
 # cp /package/admin/runit/etc/macosx/org.smarden.runit.plist \
     /Library/LaunchDaemons/
 # launchctl load /Library/LaunchDaemons/org.smarden.runit.plist
</pre>
<hr>
<address><a href="mailto:pape@smarden.org">
Gerrit Pape &lt;pape@smarden.org&gt;
</a></address>
<small>$Id$</small>
</body>
</html>