bumping another year -- now 11 years old and still a real problem
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/50093
Title:
Some sysctl's are ignored on boot
To manage notifications about this bug
** This bug is no longer a duplicate of bug 771372
procps runs too early in the boot process
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/50093
Title:
Some sysctl's are ignored on boot
To manag
*** This bug is a duplicate of bug 771372 ***
https://bugs.launchpad.net/bugs/771372
This is still a problem in 16.04 LTS/xenial. I lost a whole workday
chasing this down after an upgrade. I don't think it's a duplicate of
771372, as the above discussion indicates there is no "right" place t
*** This bug is a duplicate of bug 771372 ***
https://bugs.launchpad.net/bugs/771372
This is still happening.. Debian7.8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/50093
Title:
Some sysctl's
*** This bug is a duplicate of bug 771372 ***
https://bugs.launchpad.net/bugs/771372
bumping +3 years , still no good solution
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/50093
Title:
Some sy
*** This bug is a duplicate of bug 771372 ***
https://bugs.launchpad.net/bugs/771372
** This bug has been marked a duplicate of bug 771372
procps runs too early in the boot process
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
It seems to me it is a Debian Squeeze bug, see for example here, also
for a workaround:
http://wiki.debian.org/BridgeNetworkConnections
Strange enough...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
We've had this issue for ages. Thought we would investigate it more now
since it recently caused us a bunch of pain due to some sysctl settings
not being loaded.
It's madness that no one has looked at this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
This will probably be a bug in Ubuntu 20.04 aaron aardvark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/50093
Title:
Some sysctl's are ignored on boot
To manage notifications about this bug go to:
Just ran into this issue myself and was _quite_ surprised to see how
long this bug has been reported yet unresolved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/50093
Title:
Some sysctl's are igno
A possible workaround is putting "sysctl -p /etc/sysctl.conf" in
/etc/rc.local, which is ridiculous and doesn't even solve the problem
that networking and bridges are started *before* the sysctl settings are
applied.
It is even more ridiculous that this bug hasn't had any attention from
anyone exc
All documentation on the net referring to changing certain settings in
/etc/sysctl.conf such as net.ipv4.netfilter.ip_conntrack_max is wrong
for Ubuntu. In addition, workarounds suggesting that ordering of module
load vs. sysctl.conf execution can be helped by i.e. putting
ip_conntrack into /etc/mo
Ah, so this is why my vm.laptop_mode=5,
vm.dirty_writeback_centisecs=6000 and vm.dirty_expire_centisecs=7000
lines are totally ignored.
Workaround, anyone?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Guys somebody really should take care about this as this is not fixed
and still a problem with natty.
At least please assign to the maintainer of procps service.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
I didn't realize this was assigned to me. I don't have a recent Ubuntu
system available so I can't help with this. Sorry.
** Changed in: procps (Ubuntu)
Assignee: Yves Junqueira (yves.junqueira) => (unassigned)
--
Some sysctl's are ignored on boot
https://bugs.launchpad.net/bugs/50093
You r
I'm having the exact same problem as jollyroger and Daniel, and it was
maddening to debug.
This bug's been filed since 2006 and it's still not fixed? Anyone who
uses KVM in a bridged configuration is probably affected by it. At least
make a note of it in the procps or upstart documentation so that
This seems pretty old and I'm not sure against which version of Ubuntu
it was filed against (Sorry kinda new to this bug system) however to
appears that the problem is two fold. I'm using karmic right now which
uses upstart. I've had trouble getting the following settings to work:
=={/etc/sysctl.c
I'm having this as an issue trying to create network bridge for KVM
virtualization. Following instructions here,
http://wiki.libvirt.org/page/Networking#Debian.2FUbuntu_Bridging
Libvirt is standard in ubuntu now, and these instructions are referenced
elsewhere. Makes the whole thing a bit prob
** Changed in: procps (Ubuntu)
Assignee: (unassigned) => Yves Junqueira
--
Some sysctl's are ignored on boot
https://bugs.launchpad.net/bugs/50093
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ub
Hi.
After giving some thought on this, I don't think the complex approach
you described would work. Entries in /proc/sys may not exist even if the
module was loaded.
Take this case:
yv:~# lsmod|grep 1394
eth139418212 0
ohci1394 30800 0
ieee1394 86904
** Changed in: procps (Ubuntu)
Importance: Untriaged => Low
Status: Unconfirmed => Confirmed
--
Some sysctl's are ignored on boot
https://launchpad.net/bugs/50093
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
21 matches
Mail list logo
