Loader.conf.local Question
-
I created a loader.conf.local and added the "kern.ipc.nmbclusters=32768" line for squid tuning. How can I ensure this was merged into the loader.conf pfsense creates? The only loader.conf I see is blank (I've read this is a known bug, but it must still be using some loader.conf somewhere).
Thanks much.
-
loader.conf.local is supposed to be a separate file (not to be merged with loader.conf)
Check http://www.freebsd.org/cgi/man.cgi?query=loader.conf&sektion=5
-
I created a loader.conf.local and added the "kern.ipc.nmbclusters=32768" line for squid tuning. How can I ensure this was merged into the loader.conf pfsense creates? The only loader.conf I see is blank (I've read this is a known bug, but it must still be using some loader.conf somewhere).
Thanks much.
Hi,
1.) You can put this in loader.conf but this file will be overwrittenm after a firmwareupdate
2.) Put this in loader.conf.local will do the same job as loader.conf but will not be overwritten after firmware update
3.) don't use point 1.) and 2.). Go to System -> Advanced -> System TunablesThere you can add this and it will be saved in config.xml and will be persistent after firmware upgrade.ย :)
-
That does not work for loader tunables, only runtime tunables.
The nmbclusters change must be in loader.conf.local
-
Thanks all for the input, especially what can be put in System Tunables (because that bit was unclear from the reading I've done).
I still can't find a means to see the "load.conf" that pfsense is creating/loading at boot, but "sysctl kern.ipc.nmbclusters" shows me my changes were indeed used.
-
You can edit /boot/loader.conf and/or /boot/loader.conf.local from Diagnostics > Edit File or over ssh.
It's possible that loader.conf is empty if all defaults are being used there.