Lines Matching refs:service

36 In runit parlance a "service" is simply a directory containing a script
40 process for an individual service. Service directories themselves sit
42 directory, running one child runsv process for the service in each
44 which supervises services in subdirectories of /var/service/.
46 If /var/service/log/ exists, runsv will supervise two services,
47 and will connect stdout of main service to the stdin of log service.
50 You can debug an individual service by running its SERVICE_DIR/run script.
53 You can also run "runsv SERVICE_DIR", which runs both the service
54 and its logger service (SERVICE_DIR/log/run) if logger service exists.
55 If logger service exists, the output will go to it instead of the terminal.
57 "runsvdir /var/service" merely runs "runsv SERVICE_DIR" for every subdirectory
58 in /var/service.
77 Runs inetd. This is an example of a service with log. Log service
78 writes timestamped, rotated log data to /var/log/service/inetd/*
107 It saves new config data to /var/run/service/fw/dhcp_if.ipconf and (re)starts
108 /var/service/fw service. This example can be used as a template for other
111 This is an example of service with has a "finish" script. If downed ("sv d"),
112 "finish" is executed. For this service, it removes DHCP address from
119 Zeroconf IP service: assigns a 169.254.x.y/16 address to interface "if".
125 Watches link status of interface "if". Downs and ups /var/service/dhcp_if
126 service accordingly. In effect, it allows you to unplug/plug-to-different-network
132 If ping fails, restarts /var/service/dhcp_if service.
133 Basically, an example of watchdog service for networks which are not reliable
138 Wireless supplicant (wifi association and encryption daemon) service for
146 This is an example of *one-shot* service.
149 Uses conf/*.ipconf (static config) and /var/run/service/fw/*.ipconf
152 One-shot-ness of this service means that it shuts itself off after single run.
157 However, any dhcp/ppp/vpn or similar service can restart it anytime
159 This even works while fw service runs: if dhcp signals fw to (re)start
171 This mechanism is the reason why fw is a service, not just a script.
193 553 0:04 runsvdir -P /var/service
195 576 0:00     svlogd -tt /var/log/service/sshd
196 589 0:00     /usr/sbin/sshd -D -e -p22 -u0 -h /var/service/sshd/ssh_host_rsa_key
198 568 0:00     svlogd -tt /var/log/service/dhcp_eth0
200                 --pidfile=/var/service/dhcp_eth0/udhcpc.pid
201                 --script=/var/service/dhcp_eth0/dhcp_handler
204 573 0:01     svlogd -tt /var/log/service/ntpd
207 598 0:00     svlogd -tt /var/log/service/ifplugd_wlan0
209                 -r /var/service/ifplugd_wlan0/ifplugd_handler
213 583 0:03     svlogd -tt /var/log/service/unscd
216 591 0:00     svlogd -tt /var/log/service/dhcp_wlan0
218                 --pidfile=/var/service/dhcp_wlan0/udhcpc.pid
219                 --script=/var/service/dhcp_wlan0/dhcp_handler
222 597 0:00     svlogd -tt /var/log/service/ifplugd_eth0
224                 -r /var/service/ifplugd_eth0/ifplugd_handler
226 590 0:00     svlogd -tt /var/log/service/zcip_eth0
227 607 0:01     zcip -fvv eth0 /var/service/zcip_eth0/zcip_handler
229 604 0:00     svlogd -tt /var/log/service/ftpd
231 603 0:00     svlogd -tt /var/log/service/vpnc
233 602 0:00     svlogd -tt /var/log/service/httpd
236 627 0:00     svlogd -tt /var/log/service/supplicant_wlan0
238                 -c /var/service/supplicant_wlan0/wpa_supplicant.conf -d