freebsd-dev/etc/rc.d/sdpd

#!/bin/sh
#
# $FreeBSD$
#

# PROVIDE: sdpd
# REQUIRE: DAEMON
# BEFORE: LOGIN
# KEYWORD: nojail shutdown

. /etc/rc.subr

name="sdpd"
command="/usr/sbin/${name}"
rcvar=`set_rcvar`
required_modules="ng_btsocket"

load_rc_config $name
control="${sdpd_control:-/var/run/sdp}"
group="${sdpd_groupname:-nobody}"
user="${sdpd_username:-nobody}"
command_args="-c ${control} -g ${group} -u ${user}"

run_rc_command "$1"
Add rc.d scripts for the hcsecd(8) and sdpd(8) daemons. Put defaults into /etc/defaults/rc.conf. Both daemons can run even if no Bluetooth devices are attached to the system. Both daemons depend on Bluetooth socket layer and thus disabled by default. Bluetooth sockets layer must be either loaded as a module or compiled into kernel before the daemons can run. MFC after: 1 month 2005-10-11 19:16:48 +00:00			`#!/bin/sh`
			`#`
			`# $FreeBSD$`
			`#`

			`# PROVIDE: sdpd`
			`# REQUIRE: DAEMON`
			`# BEFORE: LOGIN`
Add the shutdown KEYWORD to those scripts that start persistent services to allow them to do a "clean" shutdown. I purposely avoided making changes to network-related stuff since the system shutting down is pretty conclusive, and there may be complicated dependencies on the network that I would rather not try to unravel. I also skipped kerberos-related stuff for the reasons above, and because I have no way to test it. 2008-07-16 19:50:29 +00:00			`# KEYWORD: nojail shutdown`
Add rc.d scripts for the hcsecd(8) and sdpd(8) daemons. Put defaults into /etc/defaults/rc.conf. Both daemons can run even if no Bluetooth devices are attached to the system. Both daemons depend on Bluetooth socket layer and thus disabled by default. Bluetooth sockets layer must be either loaded as a module or compiled into kernel before the daemons can run. MFC after: 1 month 2005-10-11 19:16:48 +00:00
			`. /etc/rc.subr`

			`name="sdpd"`
Revise hcsecd(8) and sdpd(8) rc.d scripts. - Have both scripts automatically kldload ng_btsocket(4). I did not want to do it, but its easier for users and it seems other scripts do similar things; - Assign few variables after load_rc_config, so the /etc/rc.conf overrides actually work; MFC after: 1 week 2005-11-15 20:36:26 +00:00			`command="/usr/sbin/${name}"`
			rcvar=`set_rcvar`
Use $required_modules wherever suitable. Use load_kld() in special cases. So we get rid of quite a few lines of duplicated code. 2006-12-31 10:37:18 +00:00			`required_modules="ng_btsocket"`
Revise hcsecd(8) and sdpd(8) rc.d scripts. - Have both scripts automatically kldload ng_btsocket(4). I did not want to do it, but its easier for users and it seems other scripts do similar things; - Assign few variables after load_rc_config, so the /etc/rc.conf overrides actually work; MFC after: 1 week 2005-11-15 20:36:26 +00:00
			`load_rc_config $name`
Add rc.d scripts for the hcsecd(8) and sdpd(8) daemons. Put defaults into /etc/defaults/rc.conf. Both daemons can run even if no Bluetooth devices are attached to the system. Both daemons depend on Bluetooth socket layer and thus disabled by default. Bluetooth sockets layer must be either loaded as a module or compiled into kernel before the daemons can run. MFC after: 1 month 2005-10-11 19:16:48 +00:00			`control="${sdpd_control:-/var/run/sdp}"`
Revise hcsecd(8) and sdpd(8) rc.d scripts one more time - Use _prestart rc.d method to automatically kldload ng_btsocket(4) if needed; - Rename "sdpd_user" to "sdpd_username" and "sdpd_group" to "sdpd_groupname" to avoid collision with "magic" variables; Inspired by: yar MFC after: 3 days 2005-11-22 18:51:43 +00:00			`group="${sdpd_groupname:-nobody}"`
			`user="${sdpd_username:-nobody}"`
Add rc.d scripts for the hcsecd(8) and sdpd(8) daemons. Put defaults into /etc/defaults/rc.conf. Both daemons can run even if no Bluetooth devices are attached to the system. Both daemons depend on Bluetooth socket layer and thus disabled by default. Bluetooth sockets layer must be either loaded as a module or compiled into kernel before the daemons can run. MFC after: 1 month 2005-10-11 19:16:48 +00:00			`command_args="-c ${control} -g ${group} -u ${user}"`

			`run_rc_command "$1"`