[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
howtos:slackware_admin:runit [2019/05/28 12:11 (UTC)] – Improvements and clarifications in Chapter 6 chrisabelahowtos:slackware_admin:runit [2019/05/30 12:34 (UTC)] chrisabela
Line 10: Line 10:
  
 To read on the benefits of runit, see here: http://smarden.org/runit/benefits.html To read on the benefits of runit, see here: http://smarden.org/runit/benefits.html
 +
 +Unless otherwise stated, all commands in this article are to be run by root.
  
 ===== 2. Use runit with traditional init ===== ===== 2. Use runit with traditional init =====
Line 81: Line 83:
 If you followed the previous chapter, then stop runsvdir and reverse all the changes that you made on your system. If you followed the previous chapter, then stop runsvdir and reverse all the changes that you made on your system.
  
-Remove the last line from ''/etc/inittab''+So, remove the last line from ''/etc/inittab''
  
 <code> <code>
Line 87: Line 89:
 </code> </code>
  
-Reboot:+And reboot:
  
 <code> <code>
Line 225: Line 227:
 </code> </code>
  
-In order to let the non-privileged user (say user bob) run it, change the ownership of the service directory +As a non-priviliged user (say user bob), create some directories:
- +
-<code> +
-chown bob.users /etc/sv/example +
-</code> +
- +
-As a non-priviliged user, create some directories+
  
 <code> <code>
Line 237: Line 233:
 </code> </code>
  
-Then edit a script that simulates a (finicky) service in a convenient directory; say +Then edit a ''/home/bob/runit/service.sh'' script that simulates a (finicky) service in a convenient directory; say 
  
 <code> <code>
Line 263: Line 259:
 </code> </code>
  
-Edit a file called ''/etc/sv/example/run'' and give it executable permissions+Log in back as root and edit a file called ''/etc/sv/example/run'' and give it executable permissions:
  
 <code> <code>
Line 298: Line 294:
 </code> </code>
  
-Log in as root and run the sv service to ensure that it works:+Run the service to ensure that it works:
  
 <code> <code>
-su - 
 /etc/sv/example/run /etc/sv/example/run
 </code> </code>
Line 317: Line 312:
 <code> <code>
 tail -f /home/bob/runit/logs/current  tail -f /home/bob/runit/logs/current 
-CTRL+c 
 </code> </code>
 +
 +Hit CTRL+C to exit.
 +
 +Finally, login back as root and let bob take the ownership of the whole ''/etc/sv/example/'' directory:
 +
 +<code>
 +chown -R bob.users /etc/sv/example/
 +</code>
 +
 +Now bob can manage this service with the ''sv'' command. Note that in most cases, services should belong to root, and only to root.
  
 ===== 7.  Managing Services with sv ===== ===== 7.  Managing Services with sv =====
Line 365: Line 369:
  
 <code> <code>
-sv start sshd+sv start example
  
-sv stop sshd+sv stop example
  
-sv restart sshd+sv restart example
 </code> </code>
  
 howtos:slackware_admin:runit ()