loader.conf

[kkd]

Hi

anyone could tell me the easierst way to keep my loader.conf after firmware upgrade?

Thanks
Daniel

[raulfg3]

copy to your data disk and execute a postinit script to copy fron data disk to boot disk every time you restart.

PD: better if you do not do changes in loader.conf , normally changes can be done using auxiliary parameters on WEBGUI and saved on config.xml so is persistant and do not lose in upgrades.

Post your changes to guide to best way to insert in webGUI

[kkd]

PD: better if you do not do changes in loader.conf , normally changes can be done using auxiliary parameters on WEBGUI and saved on config.xml so is persistant and do not lose in upgrades.

thank raulfg3

where is an input box for auxiliary parameters of loader.conf on WEBGUI?

[kkd]

copy to your data disk and execute a postinit script to copy fron data disk to boot disk every time you restart.

u have to reboot once again (after firmware upgrade first reboot) because it's a postinit script don't u?

[raulfg3]

try preinit instead ( you must write a scrip that control if need to be updated, some version control must be done)

[kkd]

PD: better if you do not do changes in loader.conf , normally changes can be done using auxiliary parameters on WEBGUI and saved on config.xml so is persistant and do not lose in upgrades.

thank raulfg3

where is an input box for auxiliary parameters of loader.conf on WEBGUI?

[raulfg3]

you are right , there are not auxiliary parameters in web GUI, a see your suggest to add one tab in System|Advanced viewtopic.php?f=56&t=4136

But add auxiliary parameters to ZFSkerntune is a good Idea too ( ZFSkerntune apply changes to loader.conf):

thsi is a example of my loader.conf after apply 8GB RAM in zfskerntune:

Code: Select all

kernel="kernel"
bootfile="kernel"
kernel_options=""
kern.hz="100"
hw.est.msr_info="0"
hw.hptrr.attach_generic="0"
kern.maxfiles="65536"
kern.maxfilesperproc="50000"
kern.cam.boot_delay="8000"
autoboot_delay="5"
isboot_load="YES"
zfs_load="YES"
# ZFS kernel tune
vm.kmem_size="6656M"
vfs.zfs.arc_min="5120M"
vfs.zfs.arc_max="5120M"
vfs.zfs.prefetch_disable="0"
vfs.zfs.txg.timeout="5"
vfs.zfs.vdev.max_pending="10"
vfs.zfs.vdev.min_pending="4"
vfs.zfs.write_limit_override="0"
vfs.zfs.no_write_throttle="0"

[kkd]

you are right , there are not auxiliary parameters in web GUI, a see your suggest to add one tab in System|Advanced viewtopic.php?f=56&t=4136

But add auxiliary parameters to ZFSkerntune is a good Idea too ( ZFSkerntune apply changes to loader.conf):

thsi is a example of my loader.conf after apply 8GB RAM in zfskerntune:

Code: Select all

kernel="kernel"
bootfile="kernel"
kernel_options=""
kern.hz="100"
hw.est.msr_info="0"
hw.hptrr.attach_generic="0"
kern.maxfiles="65536"
kern.maxfilesperproc="50000"
kern.cam.boot_delay="8000"
autoboot_delay="5"
isboot_load="YES".
zfs_load="YES"
# ZFS kernel tune
vm.kmem_size="6656M"
vfs.zfs.arc_min="5120M"
vfs.zfs.arc_max="5120M"
vfs.zfs.prefetch_disable="0"
vfs.zfs.txg.timeout="5"
vfs.zfs.vdev.max_pending="10"
vfs.zfs.vdev.min_pending="4"
vfs.zfs.write_limit_override="0"
vfs.zfs.no_write_throttle="0"

According to my best knowledge FreeBSD 9.x includes new event timers subsystem: eventtimers(4). Eventtimers(4) adds support for one-shot timer operation mode, when interrupts generated only when there is some work to do. That allows to not reduce kern.hz variable, so if u you use >=FreeBSD 9.x no need kern.hz="100". It's a FreeBSD 8.x heritage.

[raulfg3]

That allows to not reduce kern.hz variable, so if u you use >=FreeBSD 9.x no need kern.hz="100". It's a FreeBSD 8.x heritage.

Thanks.

I pass this info to developers.

[zoon01]

Thanks raulfg3,

if kern.eventtimer.periodic: 1 than kern.hz= can be used.

So indeed kern.hz can be removed!
With a tickless kernel kern.hz should have no effect all the time. (dynamic tick mode also called tickless mode)
I have no complains so far that there seem to be problems using tickless VMs over longer periods of time on on VMware ESX 5.0.

Regards,
zoon01

[raulfg3]

add the ability to edit / add loaders in loader.conf if latest r814 https://sourceforge.net/p/nas4free/code/814

[RedAntz]

User edited variables and settings will be saved to loader.conf.local. loader.conf will remain unchanged.

These settings will be backup/restore via usual backup of config.xml (if you add these settings vig WebGUI of course)

A restore to Factory defaults will also wipe off these settings.

[raulfg3]

User edited variables and settings will be saved to loader.conf.local. loader.conf will remain unchanged.

These settings will be backup/restore via usual backup of config.xml (if you add these settings vig WebGUI of course)

A restore to Factory defaults will also wipe off these settings.

Not sure if you test latest r814 or latter.