HardenedBSD/etc/rc.d/pflog
David E. O'Brien 8801556beb Simply things so that "#REQUIRE: FILESYSTEMS" means the file
systems are fully "ready to go".

'FILESYSTEMS' states: "This is a dummy dependency, for services which
require file systems to be mounted before starting."  However, we have
'var' which is was run after 'FILESYSTEMS' and can mount /var if it
already isn't mounted.  Furthermore, several scripts cannot use /var
until 'cleanvar' has done its thing.  Thus "FILESYSTEMS" hasn't really
meant all critical file systems are fully usable.
2012-09-11 05:04:59 +00:00

57 lines
882 B
Bash
Executable File

#!/bin/sh
#
# $FreeBSD$
#
# PROVIDE: pflog
# REQUIRE: FILESYSTEMS netif FILESYSTEMS
# KEYWORD: nojail
. /etc/rc.subr
name="pflog"
rcvar="pflog_enable"
command="/sbin/pflogd"
pidfile="/var/run/pflogd.pid"
start_precmd="pflog_prestart"
stop_postcmd="pflog_poststop"
extra_commands="reload resync"
# for backward compatibility
resync_cmd="pflog_resync"
pflog_prestart()
{
load_kld pflog || return 1
# set pflog0 interface to up state
if ! ifconfig pflog0 up; then
warn 'could not bring up pflog0.'
return 1
fi
# prepare the command line for pflogd
rc_flags="-f $pflog_logfile $rc_flags"
# report we're ready to run pflogd
return 0
}
pflog_poststop()
{
if ! ifconfig pflog0 down; then
warn 'could not bring down pflog0.'
return 1
fi
return 0
}
# for backward compatibility
pflog_resync()
{
run_rc_command reload
}
load_rc_config $name
run_rc_command "$1"