#
303975 |
|
11-Aug-2016 |
gjb |
Copy stable/11@r303970 to releng/11.0 as part of the 11.0-RELEASE cycle.
Prune svn:mergeinfo from the new branch, and rename it to RC1.
Update __FreeBSD_version.
Use the quarterly branch for the default FreeBSD.conf pkg(8) repo and the dvd1.iso packages population.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation |
#
302408 |
|
08-Jul-2016 |
gjb |
Copy head@r302406 to stable/11 as part of the 11.0-RELEASE cycle. Prune svn:mergeinfo from the new branch, as nothing has been merged here.
Additional commits post-branch will follow.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation
|
#
298514 |
|
23-Apr-2016 |
lme |
- Add descriptions to most of the rc scripts. Those are mostly taken from their daemon's manpage and probably improved. - Consistently use "filesystem" not "file system".
Approved by: bapt, brueffer Differential Revision: D452
|
#
253357 |
|
15-Jul-2013 |
des |
When stopping pfsync, remove the pfsync interface's syncpeer setting.
MFC after: 3 days
|
#
246358 |
|
05-Feb-2013 |
des |
Load the pfsync module if necessary.
Reviewed by: glebius@ MFC after: 1 week
|
#
230099 |
|
14-Jan-2012 |
dougb |
Prepare for the removal of set_rcvar() by changing the rcvar= 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.
|
#
229850 |
|
09-Jan-2012 |
glebius |
Bunch of fixes to pfsync(4) module load/unload:
o Make the pfsync.ko actually usable. Before this change loading it didn't register protosw, so was a nop. However, a module /boot/kernel did confused users. o Rewrite the way we are joining multicast group: - Move multicast initialization/destruction to separate functions. - Don't allocate memory if we aren't going to join a multicast group. - Use modern API for joining/leaving multicast group. - Now the utterly wrong pfsync_ifdetach() isn't needed. o Move module initialization from SYSINIT(9) to moduledata_t method. o Refuse to unload module, unless asked forcibly. o Improve a bit some FreeBSD porting code: - Use separate malloc type. - Simplify swi sheduling.
This change is probably wrong from VIMAGE viewpoint, however pfsync wasn't VIMAGE-correct before this change, too.
Glanced at by: bz
|
#
195026 |
|
26-Jun-2009 |
dougb |
Reverse the effect of r193198 for pf and ipfw which will once again 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.
|
#
193198 |
|
01-Jun-2009 |
dougb |
Make the pf and ipfw firewalls start before netif, just like ipfilter already does. This eliminates a logical inconsistency, and a small window where the system is open after the network comes up.
|
#
180563 |
|
16-Jul-2008 |
dougb |
As previously discussed, add the svn:executable property to all scripts
|
#
168593 |
|
10-Apr-2007 |
keramida |
Add a pfsync_syncpeer option to /etc/defaults/rc.conf and rc.conf(5), which can be used to turn off multicast pfsync support, and enable the transmission of directed PFSYNC (IP protocol: 240) packets to a specific "sync peer" host.
PR: conf/111225 Submitted by: Bas van Beek <bas@tobin.nl> Approved by: mtm, mlaier MFC after: 2 weeks
|
#
168531 |
|
09-Apr-2007 |
des |
FILESYSTEMS requires root, so requiring both of them is redundant.
|
#
168283 |
|
02-Apr-2007 |
des |
Add a dummy script, FILESYSTEMS, which depends on root and mountcritlocal 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
|
#
165683 |
|
31-Dec-2006 |
yar |
Use $required_modules wherever suitable. Use load_kld() in special cases. So we get rid of quite a few lines of duplicated code.
|
#
150835 |
|
02-Oct-2005 |
yar |
Add an rc.d script to start pfsync at the right moment of the system boot, and hook it up in the system.
The separate script is needed because in the presence of various interface lists in rc.conf ($network_interfaces, $cloned_interfaces, $sppp_interfaces, $gif_interfaces, more to come) it is hard to start them orderly, so that pfsync is brought up after its syncdev, which is required for the proper startup of pfsync.
Discussed with: mlaier on -pf MFC after: 5 days
|