SCALE needs an equivalent of tunables from CORE

[peter.m]

TrueNAS Core has the "tunables" pane in settings where one can edit either boot arguments, sysctl or rc.conf. For SCALE, we should have at least kernel params, which would be passed on to grub.conf, and the ability to pass on custom udev rules. My specific use case for both is as follows:

For the kernel params, i need net.ifnames=0, since my board has a busted BIOS which trips up systemd and it's predictable interface names, where 3 out of my 4 network interfaces contend for the same interface name. This is MAYBE fixed for systemd-247, but I don't have an OS that ships with that yet.For now, SCALE will randomly assign ethX for them, but on each boot they will get the numbers randomly. There is nothing I can do about this, since the manufacturer has EOLed the board.

For udev rules - I have 3 USB devices which I will want to use in docker containers. They are all identified as /dev/ttyUSBX, since they're all behind a serial-usb converter (a CEC controller, zigbee stick and zwave stick). I have a udev rule which hardlinkseach of them via usb identifiers to predictable names. A different usecase is setting link power managment for SATA drives, as this brings down PCH temperatures by 9C, and even impacts the CPU temperature by 3C with little difference to performance. I also use them to set the rx/tx buffers on my ethernet controllers

I can imagine some people would want sysctl to go along for the ride, just like in CORE

 

[sretalla]

System Settings | Misc | Sysctl

 

[peter.m]

System Settings | Misc | Sysctrl

Thanks, but it only does sysctl

 

[Samuel Tai]

@peter.m, you should submit a feature request for SCALE.

 

[peter.m]

https://jira.ixsystems.com/browse/NAS-109201

I'm hoping someone looks at these, I created 3 and none of them has had any feedback so far..

 

[dcplaya]

System Settings | Misc | Sysctrl

Running the newest beta and this does not seem to work. I had to drop into a shell and edit the sysctl.conf file directly for fs.file-max to work

 

[sretalla]

I have to say I just made a setting yesterday (vm.max_map_count) and came back later today to check it and it matches up in the shell, so seems to be working for me (I have never set it directly in the shell) even without a restart.

For the benefit of others, the new path under the GUI in 21.08 B2 is

System Settings | Advanced | Sysctl

 

[dcplaya]

I have to say I just made a setting yesterday (vm.max_map_count) and came back later today to check it and it matches up in the shell, so seems to be working for me (I have never set it directly in the shell) even without a restart.

For the benefit of others, the new path under the GUI in 21.08 B2 is

System Settings | Advanced | Sysctl

Is your /etc/sysctl.conf showing the change you made in the GUI?

 

[sretalla]

Is your /etc/sysctl.conf showing the change you made in the GUI?

No. It seems that file is irrelevant to SCALE.

If I check sysctl vm.max_map_count I see the value I set.

I guess the mechanism used to implement the settings isn't the built-in file, rather some kind of command (maybe sysctl -w vm.max_map_count=262144) executed by the middleware based on the DB entries set from the GUI.