summaryrefslogtreecommitdiffstats
path: root/etc/rc.d/pflog
Commit message (Collapse)AuthorAgeFilesLines
* Typo fix in commentjpaetzel2015-04-061-1/+1
| | | | MFC after: 3 days
* Bug fixes and feature addsjpaetzel2015-04-051-33/+37
| | | | | | | | | | - Remove extranious echo that breaks puppet - Handle restarts of multiple pflog devices correctly - Add the ability to perform actions on specific pflog devices. PR: 199150 Submitted by: jason.unovitch@gmail.com MFC after: 3 days
* Remove duplicate FILESYSTEMS REQUIRE from etc/rc.d/ipmon and etc/rc.d/pflogngie2014-11-301-1/+1
|
* Add support for multiple instances of ftp-proxyjpaetzel2013-11-131-7/+52
| | | | | | | and pflog devices. PR: conf/158171 Submitted by: Thomas Johnson <tom@claimlynx.com>
* Simply things so that "#REQUIRE: FILESYSTEMS" means the fileobrien2012-09-111-1/+1
| | | | | | | | | | | 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.
* Prepare for the removal of set_rcvar() by changing the rcvar=dougb2012-01-141-1/+1
| | | | | | | | | | | | | | | 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.
* Reverse the effect of r193198 for pf and ipfw which will once againdougb2009-06-261-1/+1
| | | | | | | | | | | | | | | allow them to start after netif. There were too many problems reported with this change in the short period of time that it lived in HEAD, and we are too late in the release cycle to properly shake it out. IMO the issue of having the firewalls up before the network is still a valid concern, particularly for pf whose default state is wide open. However properly solving this issue is going to take some investment on the part of the people who actually use those tools. This is not a strict reversion of all the changes for r193198 since it also included some simplification of the BEFORE/REQUIRE logic which is still valid for ipfilter and ip6fw.
* Make the pf and ipfw firewalls start before netif, just like ipfilterdougb2009-06-011-1/+1
| | | | | already does. This eliminates a logical inconsistency, and a small window where the system is open after the network comes up.
* As previously discussed, add the svn:executable property to all scriptsdougb2008-07-161-0/+0
|
* FILESYSTEMS requires root, so requiring both of them is redundant.des2007-04-091-1/+1
|
* Add a dummy script, FILESYSTEMS, which depends on root and mountcritlocaldes2007-04-021-1/+1
| | | | | | | | | | | | and takes over mountcritlocal's role as the early / late divider. This makes it far easier to add rc scripts which need to run early, such as a startup script for zfs, which is right around the corner. This change should be a no-op; I have verified that the only change in rcorder's output is the insertion of FILESYSTEMS immediately after mountcritlocal. MFC after: 3 weeks
* Use $required_modules wherever suitable. Use load_kld() in specialyar2006-12-311-9/+1
| | | | cases. So we get rid of quite a few lines of duplicated code.
* Fix a typo in a warning message.yar2006-12-311-1/+1
|
* pflog is a separate module now.mlaier2006-02-051-3/+3
| | | | | | Submitted by: Antoine Brodin PR: kern/88271 MFC after: 1 week
* Use rc.subr(8) appropriately:yar2005-10-021-44/+23
| | | | | | | | - utilize default methods instead of rolling local ones; - avoid to specify BEFORE conditions we don't really need (pflog will be REQUIRE'd by pf); - omit extra decoration from warning messages, warn() will decorate them sufficiently.
* Simplify the code by making use of 'kldstat -q -m <mod>'.pjd2005-09-241-1/+1
| | | | No objections from: mlaier
* "REQUIRE: cleanvar" for all RC's writing into /var/run.obrien2005-01-161-1/+1
|
* Remove the requirement for the FreeBSD keyword as it no longermtm2004-10-071-1/+1
| | | | | | | makes any sense. Discussed with: dougb, brooks MFC after: 3 days
* We don't have any providers of `beforenetlkm' in FreeBSD. Remove thekeramida2004-09-161-1/+1
| | | | | | dependency to it from our rc.d scripts. Approved by: mtm
* Don't rely on properly setup linker.hints to figure out that pflog is nowmlaier2004-08-311-2/+2
| | | | | | | | | part of the pf module. While here fix a comment that was c'n'ped from rc.d/pf PR: bin/71096 (partly) Submitted by: Ville-Pertti Keinonen MFC after: 2 days
* Add rc.d script to start pflogd and add rcvars etc. Also document vars inmlaier2004-04-021-0/+85
rc.conf(5) and put a sample entry to newsyslog.conf Reviewed by: -current Approved by: bms(mentor)
OpenPOWER on IntegriCloud