comparison debian/README.runit @ 511:582cb38e4eb5 insecure-nocrypto

propagate from branch 'au.asn.ucc.matt.dropbear' (head cdcc3c729e29544e8b98a408e2dc60e4483dfd2a) to branch 'au.asn.ucc.matt.dropbear.insecure-nocrypto' (head 0ca38a1cf349f7426ac9de34ebe4c3e3735effab)
author Matt Johnston <matt@ucc.asn.au>
date Thu, 06 Nov 2008 13:16:55 +0000
parents 8c2d2edadf2a
children
comparison
equal deleted inserted replaced
361:461c4b1fb35f 511:582cb38e4eb5
29 Optionally adjust the configuration of the dropbear service by editing the 29 Optionally adjust the configuration of the dropbear service by editing the
30 run script 30 run script
31 31
32 # vi /etc/dropbear/run 32 # vi /etc/dropbear/run
33 33
34 Finally enable the service by linking dropbear's service directory to 34 Finally enable the service through runit's update-service(8) program, the
35 /var/service/. The service will be started within five seconds, and 35 service will be started within five seconds, and automatically at boot
36 automatically at boot time. The sysv init script is disabled; see the 36 time, and the sysv init script will automatically be disabled; see the
37 runsvctrl(8) program for information on how to control services handled by 37 sv(8) program for information on how to control services handled by runit.
38 runit. See the svlogd(8) program on how to configure the log service. 38 See the svlogd(8) program on how to configure the log service.
39 39
40 # ln -s /etc/dropbear /var/service/ 40 # update-service --add /etc/dropbear
41 41
42 Optionally check the status of the service a few seconds later 42 Optionally check the status of the service a few seconds later
43 43
44 # runsvstat -l /var/service/dropbear 44 # sv status dropbear
45 45
46 -- Gerrit Pape <[email protected]>, Sun, 16 May 2004 15:52:34 +0000 46 -- Gerrit Pape <[email protected]>, Fri, 02 Mar 2007 20:41:08 +0000