Re: ps: bad namelist
Jerry Bell wrote: Typically this is caused by a kernel and utilities (like ps and w) being out of sync. It sounds like you don't think that is the case, though. I suppose it could be a problem with your procfs, but I'm not sure that would cause this kind of symptom. My suspicion is still on inconsistencies between the kernel and world. ps: bad namelist w: bad namelist Jerry http://www.syslog.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Ok, try the command uptime as well, I bet it will error too. It was a while ago I have had this same problem. I remember I had to remake a /dev/file ... maybe it was /dev/null ... remake /dev/null and see if that clears it up. Try this .. # cd /dev # rm null # mknod null c 2 2 # chmod 666 null ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
ps: bad namelist
Hello I wondered if any one on this list has had this happen to them and what a solution was ps: bad namelist w: bad namelist I did a trawl of Google and they talk about an incomplete upgrade etc being the cause. In my case the last thing I did was update via protupgrade Rrv clamd certainly did not do any system update or similar adventurous stuff. If this helps the box is running Freebsd 4.7 I have also checked to see if the server has been cracked this is not the case. Kind Regards Godfrey ~ Compu-Doc On-Line - http://www.compudoc.co.za Striving To Serve You Better ~ Godfrey J. Hamshire Compu-Doc On-Line 10 Perth Place Umbilo Durban 4001 Phone 08614659009 Fax 031 4651998 Cell 083 773 8776 ~ Katsumoto: A perfect blossom. You could spend your whole life searching for one, and it would not be a wasted life. ~ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ps: bad namelist
Typically this is caused by a kernel and utilities (like ps and w) being out of sync. It sounds like you don't think that is the case, though. I suppose it could be a problem with your procfs, but I'm not sure that would cause this kind of symptom. My suspicion is still on inconsistencies between the kernel and world. ps: bad namelist w: bad namelist Jerry http://www.syslog.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bad namelist
Static [EMAIL PROTECTED] writes: I'm running fbsd 4.7 in a jail environment. I am unable to run the following commands (so far) uptime, w, ps. I get the message 'bad namelist' I did some googling and found some responses from about 2 years ago stating incomplete upgrade. This was not the case, there has been no update. %w w: bad namelist %w -n w: bad namelist %uptime uptime: bad namelist %ps ps: bad namelist %ps aux ps: bad namelist FreeBSD inton.Ninja-assassin.com 4.7-RELEASE FreeBSD 4.7-RELEASE #0: Thu Feb 6 22:32:38 PST 2003 [EMAIL PROTECTED]:/usr/src/sys/compile/47 i386 Any suggestions on things to look at? Reboot has not helped. Well, I wouldn't *expect* a jail to be able to pull the process list out of the kernel. It seems like a terrible idea to allow in the first place. I can imagine a carefully limited interface for getting some of that information out, but last I recall (and admittedly that's a pretty rusty memory), those programs dove directly into kernel data structures. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bad namelist
On Sun, 13 Jul 2003, Lowell Gilbert wrote: Static [EMAIL PROTECTED] writes: I'm running fbsd 4.7 in a jail environment. I am unable to run the following commands (so far) uptime, w, ps. I get the message 'bad namelist' I did some googling and found some responses from about 2 years ago stating incomplete upgrade. This was not the case, there has been no update. %w w: bad namelist %w -n w: bad namelist %uptime uptime: bad namelist %ps ps: bad namelist %ps aux ps: bad namelist FreeBSD inton.Ninja-assassin.com 4.7-RELEASE FreeBSD 4.7-RELEASE #0: Thu Feb 6 22:32:38 PST 2003 [EMAIL PROTECTED]:/usr/src/sys/compile/47 i386 Any suggestions on things to look at? Reboot has not helped. Well, I wouldn't *expect* a jail to be able to pull the process list out of the kernel. It seems like a terrible idea to allow in the first place. I can imagine a carefully limited interface for getting some of that information out, but last I recall (and admittedly that's a pretty rusty memory), those programs dove directly into kernel data structures. For the last couple months I was able to pull ps information out, and it only showed me the processes belonging to my jail. I was also able to run the other commands that come up with bad namelist. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bad namelist
Static [EMAIL PROTECTED] writes: On Sun, 13 Jul 2003, Lowell Gilbert wrote: Static [EMAIL PROTECTED] writes: I'm running fbsd 4.7 in a jail environment. I am unable to run the following commands (so far) uptime, w, ps. I get the message 'bad namelist' I did some googling and found some responses from about 2 years ago stating incomplete upgrade. This was not the case, there has been no update. %w w: bad namelist %w -n w: bad namelist %uptime uptime: bad namelist %ps ps: bad namelist %ps aux ps: bad namelist FreeBSD inton.Ninja-assassin.com 4.7-RELEASE FreeBSD 4.7-RELEASE #0: Thu Feb 6 22:32:38 PST 2003 [EMAIL PROTECTED]:/usr/src/sys/compile/47 i386 Any suggestions on things to look at? Reboot has not helped. Well, I wouldn't *expect* a jail to be able to pull the process list out of the kernel. It seems like a terrible idea to allow in the first place. I can imagine a carefully limited interface for getting some of that information out, but last I recall (and admittedly that's a pretty rusty memory), those programs dove directly into kernel data structures. For the last couple months I was able to pull ps information out, and it only showed me the processes belonging to my jail. I was also able to run the other commands that come up with bad namelist. Hmm, yeah, okay, I took a look at it, and it definitely should work. Sorry about that. Are you sure that the code from which you built the jail is the same as the code from which you built your kernel? *Something* changed between the last time it worked and the first time it didn't; did you update any of the code inside of the jail? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
bad namelist
hi List, I'm running fbsd 4.7 in a jail environment. I am unable to run the following commands (so far) uptime, w, ps. I get the message 'bad namelist' I did some googling and found some responses from about 2 years ago stating incomplete upgrade. This was not the case, there has been no update. %w w: bad namelist %w -n w: bad namelist %uptime uptime: bad namelist %ps ps: bad namelist %ps aux ps: bad namelist FreeBSD inton.Ninja-assassin.com 4.7-RELEASE FreeBSD 4.7-RELEASE #0: Thu Feb 6 22:32:38 PST 2003 [EMAIL PROTECTED]:/usr/src/sys/compile/47 i386 Any suggestions on things to look at? Reboot has not helped. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
