Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    System tunables - Error in syslog but it works !?

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    4 Posts 3 Posters 2.0k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • N
      Nachtfalke
      last edited by

      Hi,

      I added and changed this parameter in "System tunables":

      kern.ipc.nmbclusters
      

      If I check this in the console the parameters are changed, but the syslog gives this output:

      php: /system_advanced_sysctl.php: The command '/sbin/sysctl kern.ipc.nmbclusters="65536"' returned exit code '1', the output was 'kern.ipc.nmbclusters: 65536 sysctl: kern.ipc.nmbclusters: Invalid argument'
      

      But this only happens, if I go to system tunables and click "apply changes". There is nothing in the syslog after a reboot.

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        Shouldn't that be in /boot/loader.conf.local  :-\

        See:http://forum.pfsense.org/index.php/topic,32744.0.html

        Steve

        1 Reply Last reply Reply Quote 0
        • N
          Nachtfalke
          last edited by

          Not sure.

          I thought I could place all options in the "system tunable" tab if they are "sysctl" commands.
          I find it much more comfortable to put it in the GUI than in the loader.conf.local. I know that this command will work there, too.

          And it works if I place it in "system tunables" but it is displaying an error which - in my point of view - isn't an error.

          1 Reply Last reply Reply Quote 0
          • W
            wallabybob
            last edited by

            There are a number of different constraints that apply to sysctl variables. Consider the following from my system:

            sysctl kern.ipc.nmbclusters

            kern.ipc.nmbclusters: 8000

            sysctl kern.ipc.nmbclusters=7999

            kern.ipc.nmbclusters: 8000
            sysctl: kern.ipc.nmbclusters: Invalid argument

            sysctl kern.ipc.nmbclusters="7999"

            kern.ipc.nmbclusters: 8000
            sysctl: kern.ipc.nmbclusters: Invalid argument

            sysctl kern.ipc.nmbclusters=8000

            kern.ipc.nmbclusters: 8000
            sysctl: kern.ipc.nmbclusters: Invalid argument

            sysctl kern.ipc.nmbclusters=8001

            kern.ipc.nmbclusters: 8000 -> 8001

            Looks like the only allowed modification to this parameter is to increase it (though there might also be a maximum value).

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.