* change default directory for services from /var/service/ to /service/.

Author: g-pape

doc/benefits.html

@@ -149,7 +149,7 @@ <h1>runit - benefits</h1>
 Stage 2 is packaging friendly:
 all a software package that provides a service needs to do is to include
 a <i>service directory</i> in the package, and to provide a symbolic link
-to this directory in <tt>/var/service/</tt>.
+to this directory in <tt>/service/</tt>.
 The service will be started within five seconds, and automatically at boot
 time.
 The package's install and update scripts can use the reliable control

doc/faq.html

@@ -216,12 +216,12 @@ <h1>runit - Frequently asked questions</h1>
 up and runs the service by default?
 <p>
 Answer:
-Create a symbolic link in <tt>/var/service/</tt> pointing to the service
+Create a symbolic link in <tt>/service/</tt> pointing to the service
 directory, runit will pick up the service within the next five seconds,
 and automatically start it on system boot.
 E.g.:
 <pre>
- # ln -s /etc/sv/getty-2 /var/service/
+ # ln -s /etc/sv/getty-2 /service/
 </pre>
 
 <hr>
@@ -283,13 +283,13 @@ <h1>runit - Frequently asked questions</h1>
 How do I tell runit?
 <p>
 Answer:
-Remove the symbolic link in <tt>/var/service/</tt> pointing to the service
+Remove the symbolic link in <tt>/service/</tt> pointing to the service
 directory, runit recognizes the removed service within the next five
 seconds, then stops the service, the optional log service, and finally the
 supervisor process.
 E.g.:
 <pre>
- # rm /var/service/getty-2
+ # rm /service/getty-2
 </pre>
 
 <hr>

doc/replaceinit.html

@@ -52,8 +52,8 @@ <h3>Step 3: The getties</h3>
 needed), and tell <a href="runsvdir.8.html">runsvdir</a> about the getty-5
 <i>service</i>:
 <pre>
- # mkdir -p /var/service
- # ln -s /etc/sv/getty-5 /var/service/
+ # mkdir -p /service
+ # ln -s /etc/sv/getty-5 /service/
 </pre>
 Start <i>runit</i>'s stage 2 for testing:
 <pre>
@@ -177,8 +177,8 @@ <h3>Step 3: The getties</h3>
 and tell <a href="runsvdir.8.html">runsvdir</a> about the <tt>getty-5</tt>
 <i>service</i>:
 <pre>
- # mkdir -p /var/service
- # ln -s /etc/sv/getty-5 /var/service/
+ # mkdir -p /service
+ # ln -s /etc/sv/getty-5 /service/
 </pre>
 Start <i>runit</i>'s stage 2 for testing:
 <pre>

doc/runlevels.html

@@ -25,17 +25,17 @@ <h1>runit - runlevels</h1>
  # ln -s /etc/sv/getty-5 /etc/runit/runsvdir/single/
  # ln -s default /etc/runit/runsvdir/current
 </pre>
-Copy the contents of <tt>/var/service/</tt> to
-<tt>/etc/runit/runsvdir/current/</tt> and replace <tt>/var/service/</tt>
+Copy the contents of <tt>/service/</tt> to
+<tt>/etc/runit/runsvdir/current/</tt> and replace <tt>/service/</tt>
 with a symbolic link:
 <pre>
- # cp -pR /var/service/* /etc/runit/runsvdir/current/
- # mv -f /var/service /var/service.old && \
-     ln -s /etc/runit/runsvdir/current /var/service
+ # cp -pR /service/* /etc/runit/runsvdir/current/
+ # mv -f /service /service.old && \
+     ln -s /etc/runit/runsvdir/current /service
 </pre>
 You have now created two runlevels: <tt>default</tt> and <tt>single</tt>.
 The <tt>current</tt> runlevel is <tt>default</tt>.
-It is safe to remove <tt>/var/service.old/</tt> if you don't need it anymore.
+It is safe to remove <tt>/service.old/</tt> if you don't need it anymore.
 <p>
 Finally edit <tt>/etc/runit/2</tt> to set the <tt>default</tt> runlevel when
 stage 2 starts:
@@ -47,7 +47,7 @@ <h1>runit - runlevels</h1>
  <b>runsvchdir default &gt;/dev/null</b>
 
  exec env - PATH=$PATH \
- runsvdir /var/service 'log: ...........................................................................................................................................................................................................................................................................................................................................................................................................'
+ runsvdir /service 'log: ...........................................................................................................................................................................................................................................................................................................................................................................................................'
 </pre>
 <hr>
 <a name="switch"><h3>Switching runlevels</h3></a>

doc/runscripts.html

@@ -390,7 +390,7 @@ <h3><a name="fam">A <tt>fam</tt> run script</a></h3>
 <pre>
  #!/bin/sh
  exec 2&gt;&amp;1
- sv start /var/service/portmap || exit 1
+ sv start /service/portmap || exit 1
  exec famd -T 0 -f
 </pre>
 <hr>

doc/runsv.8.html

@@ -108,9 +108,9 @@ <h2><a name='sect3'>Control</a></h2>
 <p>
 Example:
 to send a TERM signal to the socklog-unix service, either do   # sv term
-/var/service/socklog-unix<br>
+/service/socklog-unix<br>
   or<br>
-   # printf t &gt;/var/service/socklog-unix/supervise/control<br>
+   # printf t &gt;/service/socklog-unix/supervise/control<br>
  <p>
 <i><b>printf</b>(1)</i> usually blocks if no <b>runsv</b> process is running in the service
 directory. 

doc/runsvchdir.8.html

@@ -20,8 +20,8 @@ <h2><a name='sect2'>Description</a></h2>
 <b>runsvchdir</b> switches to the directory <i>/etc/runit/runsvdir/</i>,
 copies <i>current</i> to <i>previous</i>, and replaces <i>current</i> with a symlink pointing
 to <i>dir</i>. <p>
-Normally  <i>/var/service</i> is a symlink to <i>current</i>, and <i><b>runsvdir</b>(8)</i>
-is running <i>/var/service/</i>. 
+Normally  <i>/service</i> is a symlink to <i>current</i>, and <i><b>runsvdir</b>(8)</i>
+is running <i>/service/</i>. 
 <h2><a name='sect3'>Exit Codes</a></h2>
 <b>runsvchdir</b> prints an error message and
 exits 111 on error. <b>runsvchdir</b> exits 0 on success. 

doc/sv.8.html

@@ -21,7 +21,7 @@ <h2><a name='sect2'>Description</a></h2>
 <i>services</i> consists of one or more arguments,
 each argument naming a directory <i>service</i> used by <i><b>runsv</b>(8)</i>. If <i>service</i> doesn&rsquo;t
 start with a dot or slash, it is searched in the default services directory
-<i>/var/service/</i>, otherwise relative to the current directory. <p>
+<i>/service/</i>, otherwise relative to the current directory. <p>
 <i>command</i> is one
 of up, down, status, once, pause, cont, hup, alarm, interrupt, 1, 2, term,
 kill, or exit, or start, stop, restart, shutdown, force-stop, force-reload,
@@ -157,7 +157,7 @@ <h2><a name='sect7'>Environment</a></h2>
 
 <dt><b>SVDIR</b> </dt>
 <dd>The environment variable $SVDIR overrides the
-default services directory <i>/var/service/</i>. </dd>
+default services directory <i>/service/</i>. </dd>
 
 <dt><b>SVWAIT</b> </dt>
 <dd>The environment variable

doc/useinit.html

@@ -21,10 +21,10 @@ <h1>runit - use with traditional init</h1>
 <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>:
+<tt>/service/</tt>:
 <pre>
  # install -m0750 /package/admin/runit/etc/2 /sbin/runsvdir-start
- # mkdir -p /var/service
+ # mkdir -p /service
 </pre>
 <hr>
 <a href="#sysv">How to use with sysvinit and inittab</a><br>

doc/utmpset.8.html

@@ -23,7 +23,7 @@ <h2><a name='sect2'>Description</a></h2>
 other services. <p>
 To enable local login accounting, add <b>utmpset</b> to the <i><b>getty</b>(8)</i>
 <i>finish</i> scripts, e.g.: <p>
- $ cat /var/service/getty-5/finish<br>
+ $ cat /service/getty-5/finish<br>
   #!/bin/sh<br>
   exec utmpset -w tty5<br>
   $<br>