comparison debian/README.runit @ 70:b0316ce64e4b

Merging in the changes from 0.41-0.43 main Dropbear tree
author Matt Johnston <matt@ucc.asn.au>
date Thu, 12 Aug 2004 16:41:58 +0000
parents
children 8c2d2edadf2a
comparison
equal deleted inserted replaced
69:59d16db56e9f 70:b0316ce64e4b
1 Using the dropbear SSH server with runit's services supervision
2 ---------------------------------------------------------------
3
4 The dropbear SSH server is perfectly suited to be run under runit's
5 service supervision, and this package already has prepared an adequate
6 service directory. Follow these steps to enable the dropbear service
7 using the runit package.
8
9 If not yet installed on your system, install the runit package, and make
10 sure its service supervision is enabled (it's by default)
11
12 # apt-get install runit
13
14 Make sure the dropbear service normally handled through the sysv init
15 script is stopped
16
17 # /etc/init.d/dropbear stop
18
19 Create the system user ``dropbearlog'' which will run the logger service,
20 and own the logs
21
22 # adduser --system --home /var/log/dropbear --no-create-home dropbearlog
23
24 Create the log directory and make the newly created system user the owner
25 of this directory
26
27 # mkdir -p /var/log/dropbear && chown dropbearlog /var/log/dropbear
28
29 Optionally adjust the configuration of the dropbear service by editing the
30 run script
31
32 # vi /etc/dropbear/run
33
34 Finally enable the service by linking dropbear's service directory to
35 /var/service/. The service will be started within five seconds, and
36 automatically at boot time. The sysv init script is disabled; see the
37 runsvctrl(8) program for information on how to control services handled by
38 runit. See the svlogd(8) program on how to configure the log service.
39
40 # ln -s /etc/dropbear /var/service/
41
42 Optionally check the status of the service a few seconds later
43
44 # runsvstat -l /var/service/dropbear
45
46 -- Gerrit Pape <[email protected]>, Sun, 16 May 2004 15:52:34 +0000