Re: Problems with package "sys-apps/systemd-utils" version 259.3
Michael <[email protected]> Sat, 11 Apr 2026 18:08:34 +0100
| Newsgroups | gmane.linux.gentoo.user |
|---|---|
| Message-ID | <3415619.44csPzL39Z@rogueboard> |
On Saturday, 11 April 2026 17:29:55 British Summer Time you wrote: > Michael, > > On Friday, 2026-04-10 16:51:15 +0100, you wrote: > > ... > > I think you'll find this file is missing from your system? > > > > ~ $ ls -la /proc/sys/net/core/default_qdisc > > -rw-r--r-- 1 root root 0 Apr 10 16:27 > > /proc/sys/net/core/default_qdisc > No, the file exists but contains the default value: > > $ cat /proc/sys/net/core/default_qdisc > pfifo_fast > $ > > And the help texts for kernel configuration variables "CONFIG_*_CODEL" > clearly state > > CONFIG_NET_SCH_FQ_CODEL: > > Say Y here if you want to use the FQ Controlled Delay (FQ_CODEL) > packet scheduling algorithm. > > To compile this driver as a module, choose M here: the module > will be called sch_fq_codel. > > If unsure, say N. > > CONFIG_NET_SCH_DEFAULT: > > Support for selection of default queuing discipline. > > Nearly all users can safely say no here, and the default > of pfifo_fast will be used. Many distributions already set > the default value via /proc/sys/net/core/default_qdisc. > > If unsure, say N. > > So should I _really_ set these kernel configuration variables? No, this was just an example from one of my gentoo systems. It runs sys-apps/systemd-utils-259.3, but it does not have the warning you get in your log. > > ... > > > > > ... > > > I'm currently running kernel "sys-kernel/gentoo-sources-6.18.18" > > > but I also tried both versions of package > > > "sys-apps/systemd-utils" on my pre- vious kernel > > > "sys-kernel/gentoo-sources-6.18.12" with identical results. > > Sorry, but regarding the kernel versions I goofed and picked the > wrong data from my notes: my currently running kernel is version > 6.18.12 while the previous kernel was version 6.12.58. > > Meanwhile, I found at least one difference between the version 259.3 > and version 255.18 of package "sys-apps/systemd-utils": > > With version 259.3: > > # grep _qdisc /usr/lib/sysctl.d/50-default.conf > -net.core.default_qdisc = fq_codel > # > > which seems reasonable, provided my interpretation of the leading "-" > as logical "not" is correct. Well, I have the same here: ~ # grep -i qdisc -r /usr/lib/sysctl.d/ /usr/lib/sysctl.d/50-default.conf:-net.core.default_qdisc = fq_codel > However, under version 255.18, where everything now seems to work: > > # grep _qdisk /usr/lib/sysctl.d/50-default.conf > grep: /usr/lib/sysctl.d/50-default.conf: No such file or directory > # > > Could the configuration provided in new file "50-default.conf" be > buggy? > > Sincerely, > Rainer Sorry, I don't know. I was just comparing with what I get here and sys- apps/systemd-utils does not seem to be the cause of it. Unless it only goes into a tailspin with the default FIFO option? :-/ FWIW, I also don't get your problem on another system which has NFT_FLOW_OFFLOAD [=n].
signature.asc
(application/pgp-signature, 870 B)
-----BEGIN PGP SIGNATURE----- iQJPBAABCAA5FiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmnagBIbFIAAAAAABAAO bWFudTIsMi41KzEuMTIsMiwyAAoJELHqqvbClWcZAeoP/0jm334TOwDy/o7aXvkr CClzd5zhUmOgO4/rQyfzYSh5lxUJ/2mo7GhWek2E/FRWx5k4QD4c79TT+7YWLBAC E8RSboKAsZ7ukJiD1ADF8xyyKUCdCH0+w1QJo/8Ir8zRL6Dqn43QYiQuLnv7uF6R bdga8P5PE/ZDGCa6gpGYaSr3R/XKoS3AVtjZXvi4pOKAdRTbD5AD1reBpX7p8kZS WDEtbo9jYaIg9FbgY9uT1qFDuMnLKVXOLqNBrGdGIOTAfOsw9sQRacYLvi5f23XZ mfxqlyPDzSSQZMPwXmCowNyyvlF4KDnkAQ21teVQXMUP+iiIKNHCWLGXruOeEVn/ zG+ZIQE9EMGK6tdJn++HwNfMD392pW2HpW3eIeJPsApm/WEHHgSrFfIbTKEr4JIw cFLefm6Ob3XT6HBx1vDV4tCOaywkzAtKaHX/52dYTWJkpDUwrA0Uh47rJgspll8b SSQiKOYksaHqtFSWP0TBk1wUU7d5PSXw6Bxl94A57ElhbhFrYAIb4DktXcb52Q+w K7O+KAucFEZ7mytOHSZI4iT2WmuTf0ZQooAUOFFW+u6Uma9Pddt20DgWvMxbJvSa OchagDeRo6N7boZl7FgLGQoCwGHw5S4MvKRFXTt7APfS5WsIAKaj1eFkXGaxwZAX 7kHedvLvU3IZsmj/5XLo9syD =84Pg -----END PGP SIGNATURE-----