Description of problem: sysctl reports strange error messages Version-Release number of selected component (if applicable): procps-3.2.3-5 How reproducible: Always Steps to Reproduce: 1. sysctl -a >/dev/null Actual Results: One box running FC3 (2.6.9-1.724_FC3) # sysctl -a >/dev/null error: unknown error 22 reading key 'net.ipv6.route.flush' error: unknown error 22 reading key 'net.ipv4.route.flush' error: unknown error 22 reading key 'fs.binfmt_misc.register' Other box running FC3 (2.6.9-1.681_FC3) # sysctl -a >/dev/null error: unknown error 25 reading key 'dev.parport.parport0.autoprobe3' error: unknown error 25 reading key 'dev.parport.parport0.autoprobe2' error: unknown error 25 reading key 'dev.parport.parport0.autoprobe1' error: unknown error 25 reading key 'dev.parport.parport0.autoprobe0' error: unknown error 25 reading key 'dev.parport.parport0.autoprobe' error: unknown error 22 reading key 'net.ipv6.route.flush' error: unknown error 22 reading key 'net.ipv4.route.flush' error: unknown error 22 reading key 'fs.binfmt_misc.registe Expected Results: Not such strange error messages, in FC2 I don't get them.
The problem with error 22 is common (see google: "/proc/sys/net/ipv4/route/flush Invalid argument" or "cat /proc/sys/net/ipv4/route/flush"). The rest will fixed.
The bugfix will available in FC-4 (or in the current devel branch).
I get the following anyway...could this also please fixed? error: unknown error 22 reading key 'net.ipv6.route.flush' error: unknown error 22 reading key 'net.ipv4.route.flush'
No. I have no idea how fix it. See comment #1
Note: small change is the next upstream release where it produces error: "Invalid argument" reading key "net.ipv4.route.flush" I will release 3.2.5 as soon as possible.
*** Bug 146534 has been marked as a duplicate of this bug. ***
*** Bug 152435 has been marked as a duplicate of this bug. ***
*** Bug 150807 has been marked as a duplicate of this bug. ***
It looks it's old story in linux kernel: http://lkml.org/lkml/2000/1/21/116 http://lkml.org/lkml/2000/1/22/164 http://lkml.org/lkml/2000/1/23/29 We need some common way how detect which files from /proc/sys are write-only. I agree that files in /proc/sys that cannot be read should not be +r. For example: #ls -la /proc/sys/net/ipv4/route/flush -rw-r--r-- 1 root root 0 Apr 25 13:07 /proc/sys/net/ipv4/route/flush # cat /proc/sys/net/ipv4/route/flush cat: /proc/sys/net/ipv4/route/flush: Invalid argument It's problem in all our kernels and distributions.
I've fixed up net and parport entries. They'll be mode 0200 in the next builds. However, /proc/sys/fs/binfmt_misc/register is already mode 0200, and the warning above shows, so there's still something not right in procps if its trying to read files listed as --w------
Thanks. The command 'sysctl' doesn't check modes yet. I want to fix it in the next build.
Fixed in FC-4. I don't want to fix it in old distributions (<=FC-3, <=RHEL4), it could be a regression problem and the old kernels don't export /proc/sys write-only files with the right mode.