Browse Source

We don't need a conditional around the pfsync start.

(As a reminder to others who spot this weirdness later and get
confused like I did:  netstart never starts pfsync automatically,
because it would screw the states.  That is why there is this 2nd
manual netstart run for pfsync)
ok mpf
OPENBSD_5_0
deraadt 13 years ago
parent
commit
cc05871892
1 changed files with 2 additions and 4 deletions
  1. +2
    -4
      src/etc/rc

+ 2
- 4
src/etc/rc View File

@ -1,4 +1,4 @@
# $OpenBSD: rc,v 1.360 2011/07/07 22:30:37 robert Exp $
# $OpenBSD: rc,v 1.361 2011/07/07 22:47:30 deraadt Exp $
# System startup script run by init on autoboot # System startup script run by init on autoboot
# or after single-user. # or after single-user.
@ -323,9 +323,7 @@ if [ X"${pf}" != X"NO" ]; then
pfctl -f ${pf_rules} pfctl -f ${pf_rules}
fi fi
# bring up pfsync after the working ruleset has been loaded # bring up pfsync after the working ruleset has been loaded
if [ -f /etc/hostname.pfsync0 ]; then
. /etc/netstart pfsync0
fi
. /etc/netstart pfsync0
fi fi
mount -s /usr >/dev/null 2>&1 mount -s /usr >/dev/null 2>&1


Loading…
Cancel
Save