sysctl variables changes becoming active on upadting packages?
Hi, we are wondering if sysctl values in on of the /etc/sysctl* directories change via a packageupdate, if they should become active immediately, or only ever on next reboot. e.g. running /usr/lib/systemd/systemd-sysctl in %post of such packages would make them active, but could overwrite admin set values. Ciao, Marcus
On Mon, Feb 21, Marcus Meissner wrote:
Hi,
we are wondering if sysctl values in on of the /etc/sysctl* directories change via a packageupdate, if they should become active immediately, or only ever on next reboot.
e.g. running /usr/lib/systemd/systemd-sysctl in %post of such packages would make them active, but could overwrite admin set values.
If you use a transactional system (so with transactional-update), you are not allowed to do the settings immediately, only with the next reboot. Else you could break the running system. If you update packages in a running system, it's the question why you change this values. If this is necessary for the updated workload, then you need to change it during upgrade, else the workload will not start afterwards. If this is for other reasons: it's depends. So I don't see a simple yes/no here. Between, it's /usr/lib/sysctl.d/, not /etc/sysctl.d/ Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany Managing Director: Ivo Totev (HRB 36809, AG Nürnberg)
participants (2)
-
Marcus Meissner
-
Thorsten Kukuk