sysctl seg-fault. How to diagnose?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I have 3 systems running RH in a small network. Hardware wise these boxes are very different, but after some initial problems upgrading one box from RH62 to RH8 (the other two boxes were new-installs) things are running fine.

However, I've found that running sysctl -a on one box (PII-400) results in a segmentation fault:

[root@dilbert etc]# sysctl -a
sunrpc.nlm_debug = 0
sunrpc.nfsd_debug = 0
sunrpc.nfs_debug = 0
sunrpc.rpc_debug = 0
abi.fake_utsname = 0
abi.trace = 0
abi.defhandler_libcso = 68157441
abi.defhandler_lcall7 = 68157441
abi.defhandler_elf = 0
abi.defhandler_coff = 117440515
Segmentation fault

And I have NO clue how to diagnose the sysctl program.
How would I proceed to find out what's causing this?
The sysctl works just fine on the other boxes.

In addition, I can ask for keys not shown (like kernel.hostname) and get a proper responce. I see no errors in the boot-log for the box either.

Best Regards
  Peter Larsen



-- 
Psyche-list mailing list
Psyche-list@redhat.com
https://listman.redhat.com/mailman/listinfo/psyche-list

[Index of Archives]     [Fedora General Discussion]     [Red Hat General Discussion]     [Centos]     [Kernel]     [Red Hat Install]     [Red Hat Watch]     [Red Hat Development]     [Red Hat 9]     [Gimp]     [Yosemite News]

  Powered by Linux