Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
"sysctl.d docs clearly explain this is a known issue with clearly
documented ways to work around it"
Try googling "how to disable ipv6 in ubuntu". The results suggest that
the word "clearly" is misused.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
As procps has been replaced by systemd in recent releases (at least the
sysctl service part), I'm switching the target package to systemd.
Also, I'm changing this to wishlist as this isn't actually a bug; from
the sysctl.d manpage:
"Many sysctl parameters only become available when certain
Just to reiterate, I'm only marking procps as 'wontfix' because the
sysctl service used in all current releases comes from systemd, *not*
the procps package, so there is nothing to 'fix' in the procps package.
Also, before people get upset, I've only marked this as Wishlist because
the sysctl.d
Still seeing this in bionic 18.04.3 with the following kernel and procps
package.
ii procps 2:3.3.12-3ubuntu1.2
amd64/proc file system utilities
kernel 5.4.0-62-generic
--
You received this bug notification because you are a member of Ubuntu
Touch
** Changed in: procps (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/50093
Title:
Some sysctls
Still no fix? I have just ran into the same problem...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/50093
Title:
Some sysctls are ignored on boot
Status in procps
I have added a file in /etc/sysctl.d/98-* setting up NFS sysctl
parameters and they were not loaded by default until I have added:
nfsd
to /etc/modules, re-generated the initramfs and rebooted, checking it
again, when it worked.
** Changed in: procps (Ubuntu)
Assignee: (unassigned) =>
I have the same problem in Debian 9 Stretch, net.netfilter.nf_conntrack_max and
net.nf_conntrack_max does not apply after reboot. The pure solution is load
module nf_conntrack before sysctl. You can do this with the command:
echo "nf_conntrack" >> /etc/modules
--
You received this bug
Actually, the line which works without specifying a PATH in a cron.d
file is the following:
@reboot root /bin/sleep 5 && /sbin/sysctl --system
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
I feel it's important to add that the very last comment (Stanley
Sisneros (stanley-sisneros) wrote on 2018-05-30) is wrong, and the right
workaround is by Tomasz Konefal (twkonefal-j) wrote on 2018-05-07.
That is, add this to crontab:
@reboot root sleep 5 && sysctl --system
--
You received this
In Ubuntu 16.04 I made this work by adding the following to crontab -e
@reboot sleep 15; /sbin/sysctl -p
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/50093
Title:
Some
A workaround for this that we're using now is to put the sysctl
processing into crontab after reboot.
e.g.
@reboot root sleep 5 && sysctl --system
Maybe one day someone will fix this bug :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Summary changed:
- Some sysctl's are ignored on boot
+ Some sysctls are ignored on boot
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/50093
Title:
Some sysctls are
14 matches
Mail list logo
