This bug was fixed in the package procps - 2:3.3.15-2ubuntu1
---
procps (2:3.3.15-2ubuntu1) cosmic; urgency=medium
* Merge from Debian unstable. Remaining changes:
- debian/sysctl.d (Ubuntu-specific):
+ 10-console-messages.conf: stop low-level kernel messages on console.
Right -- systemd have just-now agreed to set the change in their upstream
systemd sysctl files :-
https://github.com/systemd/systemd/commit/6f130e85c76cfc2c58ba31f90d2ac3800866c1dd
I notice, however, that ubuntu's systemd pkg 'strips most those settings
out', in 18.04 currently only carrying the
It would appear that the path-of-least-resistance at present, is
systemd, poettering which is what is (for systemd-booters) where
fq_codel is getting turned-on in ubuntu.
This raises a wider-issue about bringing systemd-provided sysctl-
defaults into procps more widely [systemd has introduced
I'm dropping the redundant setting of syncookies from the delta but IMO
ECN should be enabled upstream or in Debian instead of adding a delta
for it in Ubuntu.
Please try to get ECN enabled at upstream or at Debian, we have plenty
of time before the next (LTS) release in case we have to fall back
(fwiw, fq_codel queuing is now being turned-on in bionic (at least) by systemd,
confusingly!).
https://github.com/systemd/systemd/commit/e6c253e363dee77ef7e5c5f44c4ca55cded3fd47
Possibly, turning on ECN might more likely happen there first, but I would like
the procps updated for those using
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: procps (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773157
Title:
I've been running with tcp_ecn=1 for years with no issue. Since ECN
marking is making its way into more and more places, enabling it by
default makes sense. In particular, it would go well with the recent
addition of FQ-CoDel as the default queue management algorithm :)
--
You received this bug
