3645513107
assignments to the literal values it would have returned.
The concept of set_rcvar() was nice in theory, but the forks
it creates are a drag on the startup process, which is especially
noticeable on slower systems, such as embedded ones.
During the discussion on freebsd-rc@ a preference was expressed for
using ${name}_enable instead of the literal values. However the
code portability concept doesn't really apply since there are so
many other places where the literal name has to be searched for
and replaced. Also, using the literal value is also a tiny bit
faster than dereferencing the variables, and every little bit helps.
49 lines
708 B
Bash
Executable File
49 lines
708 B
Bash
Executable File
#!/bin/sh
|
|
#
|
|
# $FreeBSD$
|
|
#
|
|
|
|
# PROVIDE: pfsync
|
|
# REQUIRE: FILESYSTEMS netif
|
|
# KEYWORD: nojail
|
|
|
|
. /etc/rc.subr
|
|
|
|
name="pfsync"
|
|
rcvar="pfsync_enable"
|
|
start_precmd="pfsync_prestart"
|
|
start_cmd="pfsync_start"
|
|
stop_cmd="pfsync_stop"
|
|
required_modules="pf"
|
|
|
|
pfsync_prestart()
|
|
{
|
|
case "$pfsync_syncdev" in
|
|
'')
|
|
warn "pfsync_syncdev is not set."
|
|
return 1
|
|
;;
|
|
esac
|
|
return 0
|
|
}
|
|
|
|
pfsync_start()
|
|
{
|
|
local _syncpeer
|
|
|
|
echo "Enabling pfsync."
|
|
if [ -n "${pfsync_syncpeer}" ]; then
|
|
_syncpeer="syncpeer ${pfsync_syncpeer}"
|
|
fi
|
|
ifconfig pfsync0 $_syncpeer syncdev $pfsync_syncdev $pfsync_ifconfig up
|
|
}
|
|
|
|
pfsync_stop()
|
|
{
|
|
echo "Disabling pfsync."
|
|
ifconfig pfsync0 -syncdev down
|
|
}
|
|
|
|
load_rc_config $name
|
|
run_rc_command "$1"
|