[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:20 (UTC)] – [7.1. Stop/Start/Restart] chrisabelahowtos:slackware_admin:runit [2019/05/29 11:40 (UTC)] – chrisabela
Line 81: Line 81:
 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 87:
 </code> </code>
  
-Reboot:+And reboot:
  
 <code> <code>
Line 317: Line 317:
 <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, 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 533: Line 542:
 <!-- Please do not modify anything below, except adding new tags.--> <!-- Please do not modify anything below, except adding new tags.-->
 {{tag>init runit}} {{tag>init runit}}
 +

Trace:

howtos:slackware_admin:runit ()