Proc Size Mismatch

2003-08-25 Thread Ian Barnes
, fine, no problem, did it manually, and got it to boot. Now when i login and try and type something, these are the errors im getting: [EMAIL PROTECTED] ~ # ps -ax ps: proc size mismatch (27664 total, 1056 chunks) [EMAIL PROTECTED] ~ # [EMAIL PROTECTED] ~ # killall -HUP named proc size mismatch

Re: Proc Size Mismatch

2003-08-25 Thread Joshua Oreman
On Mon, Aug 25, 2003 at 07:14:03PM +0200 or thereabouts, Ian Barnes wrote: Hi, I am running a 4.7 stable machine on a p1 120. With 16meg of ram. ITs function is a secondary DNS server. IT has been running very stable until this weekend. The machine froze for some or other reason. Upon

ps: proc size mismatch

2003-02-22 Thread Chris Pepper
I last did a buildworld, buildkernel, installkernel, installworld in December (from current STABLE sources via cvsup). I tried again a few weeks ago and today, and after booting to single-user get errors from ps about /proc (ps: proc size mismatch). uname from my working kernel world

Re: ps: proc size mismatch

2003-02-22 Thread Giorgos Keramidas
# mergemaster found no changes # mergemaster -p # no changes found # make installkernel The proc size mismatch you're seeing is because your kernel and userland is not in sync. Reboot. Enter single user mode. Run 'installworld'. If you suspect 'installworld' can fail in the middle of it all

Re: ps: proc size mismatch

2003-02-22 Thread Mike Meyer
In [EMAIL PROTECTED], Chris Pepper [EMAIL PROTECTED] typed: I know that, because I haven't done make installworld yet, but I'm trying to validate the new kernel first. Unfortunately, there isn't much info on how to validate the kernel (if it boots to the shell, is it fine??). It's a pretty

Re: ps: proc size mismatch

2003-02-22 Thread Chris Pepper
; make buildkernel ~/buildkernel-20030221.log # mergemaster found no changes # mergemaster -p # no changes found # make installkernel The proc size mismatch you're seeing is because your kernel and userland is not in sync. Reboot. Enter single user mode. Run 'installworld'. If you suspect

proc size mismatch (73920 total, 1060 chunks)

2003-02-20 Thread Dean Gunther
I keep getting the above error when I try to do things like ps or even top. I have looked at everyting I can think of, but haven't been able to figure out what is wrong. I tried rebooting the server, but to no avail. Any ideas would be greatly appreciated. TIA Dean Gunther To Unsubscribe:

Re: proc size mismatch (73920 total, 1060 chunks)

2003-02-20 Thread Jeff Jirsa
On Thu, 20 Feb 2003, Dean Gunther wrote: I keep getting the above error when I try to do things like ps or even top. I have looked at everyting I can think of, but haven't been able to figure out what is wrong. I tried rebooting the server, but to no avail. Any ideas would be greatly

proc size mismatch

2003-02-03 Thread Harold Mackey
It appears that my kernel is 4.7-STABLE and cvsup has downloaded 4.7-RELEASE-pl2. I need to get my system synced up again and STABLE. Any how-to's out there? Thanks Harold A. Mackey MUSC Digestive Disease Center 96 Jonathan Lucas Street Suite 210 CSB Charleston, SC 29403 ph 843-792-4858 fx

Re: proc size mismatch

2003-02-03 Thread Kent Stewart
On Monday 03 February 2003 08:41 am, Harold Mackey wrote: It appears that my kernel is 4.7-STABLE and cvsup has downloaded 4.7-RELEASE-pl2. I need to get my system synced up again and STABLE. Any how-to's out there? There isn't a tag for 4.7-stable. It is only RELENG_4 and slides with new

Re: proc size mismatch

2003-02-03 Thread Bill Moran
Harold Mackey wrote: It appears that my kernel is 4.7-STABLE and cvsup has downloaded 4.7-RELEASE-pl2. I need to get my system synced up again and STABLE. Any how-to's out there? The handbook's section on staying current. When you cvsup again, you should use RELENG_4 instead of RELENG_4_7 for