Loader.conf diferente do System tunables



  • Olá pessoal,

    Depois que atualizei meu firewall para a versão 2.1.3R, ele começou a gerar esses logs.  Estes valores setei na versão 2.1.1, agora nesta nova versão apresenta esses logs:

    Jun 30 11:01:15 php: /system_advanced_sysctl.php: The command '/sbin/sysctl vm.kmem_size="1024"' returned exit code '1', the output was 'sysctl: oid 'vm.kmem_size' is a read only tunable sysctl: Tunable values are set in /boot/loader.conf'

    Jun 30 11:01:15 php: /system_advanced_sysctl.php: The command '/sbin/sysctl kern.ipc.nmbclusters="131072"' returned exit code '1', the output was 'kern.ipc.nmbclusters: 131072 sysctl: kern.ipc.nmbclusters: Invalid argument'

    Jun 30 11:01:15 php: /system_advanced_sysctl.php: The command '/sbin/sysctl hw.igb.num_queues="1"' returned exit code '1', the output was 'sysctl: oid 'hw.igb.num_queues' is a read only tunable sysctl: Tunable values are set in /boot/loader.conf'

    Notei também que no loader.conf, os dados foram alterados automaticamente.

    [2.1.3-RELEASE][root@fw.local]/boot(3): cat loader.conf
    autoboot_delay="3"
    vm.kmem_size="435544320"
    vm.kmem_size_max="535544320"
    kern.ipc.nmbclusters="0"
    hw.usb.no_pf="1"

    Devo apagar as alterações que fiz em System Tunables e manter essas em loader.conf?

    ![system tunables.png](/public/imported_attachments/1/system tunables.png)
    ![system tunables.png_thumb](/public/imported_attachments/1/system tunables.png_thumb)


Log in to reply