Hi
I have a setting to disable ipv6 in /etc/sysctl.conf and it is ignored at boot
I have to manually run
sudo sysctl -p
and the settings I've added (or are added by suse?) are then appied
I've had a look back though posts on these forums and cannot see an actual answer that works (including a thread from 2013)
/etc/sysctl.conf is defintely link to from /usr/lib/sysctl.d/99-sysctl.conf -> /etc/sysctl.conf
One thread suggested
But I got a response of
Running
tells me:
Running
Gives me what I want and reads /etc/sysctl.conf
But this does not happen at boot
Why?
In debian (which I use at work on multiple VMs, actual hardware etc of all OSes dating back years) this just works
But not in Tumbleweed
There is obviously some step I am missing that involves more than just putting an entry in /etc/sysctl.conf
(and has been for a while?)
But it should be possible to just add an entry in /etc/sysctl.conf and reboot and it to just work by default
If it doesn't, then is it a bug?
It really should not be a question of RTFM because manually running
works
Regards
I have a setting to disable ipv6 in /etc/sysctl.conf and it is ignored at boot
I have to manually run
sudo sysctl -p
and the settings I've added (or are added by suse?) are then appied
I've had a look back though posts on these forums and cannot see an actual answer that works (including a thread from 2013)
/etc/sysctl.conf is defintely link to from /usr/lib/sysctl.d/99-sysctl.conf -> /etc/sysctl.conf
Code:
ls -l /usr/lib/sysctl.d/99-sysctl.conf
lrwxrwxrwx 1 root root 16 Mar 6 21:05 /usr/lib/sysctl.d/99-sysctl.conf -> /etc/sysctl.confCode:
chkconfig -a boot.sysctlCode:
boot.sysctl: unknown serviceCode:
sudo systemctl enable systemd-sysctl.serviceCode:
The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
instance name specified.Code:
sudo sysctl -pBut this does not happen at boot
Why?
In debian (which I use at work on multiple VMs, actual hardware etc of all OSes dating back years) this just works
But not in Tumbleweed
There is obviously some step I am missing that involves more than just putting an entry in /etc/sysctl.conf
(and has been for a while?)
But it should be possible to just add an entry in /etc/sysctl.conf and reboot and it to just work by default
If it doesn't, then is it a bug?
It really should not be a question of RTFM because manually running
Code:
sudo sysctl -pRegards