From owner-freebsd-stable Sun Apr 11 1:18:18 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freed.libdns.qc.ca (derby.JSP.UMontreal.CA [132.204.45.26]) by hub.freebsd.org (Postfix) with ESMTP id DAF9014D98 for ; Sun, 11 Apr 1999 01:18:12 -0700 (PDT) (envelope-from spidey@libdns.qc.ca) Received: from localhost (spidey@localhost) by freed.libdns.qc.ca (8.9.3/8.9.3) with SMTP id EAA00318; Sun, 11 Apr 1999 04:15:59 -0400 (EDT) (envelope-from spidey@libdns.qc.ca) X-Authentication-Warning: freed.libdns.qc.ca: spidey owned process doing -bs Date: Sun, 11 Apr 1999 04:15:59 -0400 (EDT) From: Spidey Reply-To: Spidey To: FreeBSD Stable Cc: Eric Griff Subject: SOLVED. Re: ps problems (explained) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I solved my ps problems, and I want to share my happiness with the list :) - I cvsupped the sources of -stable on Apr 10 14:07. - I made a buildworld in multi-user. - I made an installworld after in single-user mode. - I compile a GENERIC kernel and update /dev, /etc and /stand. - ps still gives me the creeps. ("bad namelist"). - uptime is messed up as said below. - I move /var/run/utmp to /tmp then touch /var/run/utmp. - uptime is back on the track. - I compile a custom kernel without nfs, vm86, bpfilter, ether, pca0, speaker from my previous kernel version. - This one works great! ps is working again!!! I do think that the problems was first due to a installworld in multi-user mode, which probably corrupted /var/run/utmp and the /proc filesystem as I tried to remove /proc from fstab and put it back again to make ps work. I'm not sure though... It could be just rebuilding the kernel that made ps work as I did both at the same time. So the lesson is: - installworld or simple world in single-user mode. Always. - that is all :) - oh yeah, and read the error messages of the programs :)) On Fri, 9 Apr 1999, Spidey wrote: > I don't know if and how I should make a bug report about this, as I don't > know for sure what exactly the problem is... What I know, however, is that > my daily script is also bugged: > > Local system status: > uptime: /dev//umount: /cdrom: not currently mounted > umount: No such file or directory > uptime: /dev//: /proc: not currently mounted > umount: /var:: No such file or directory > uptime: /dev// not currently mounted > umount: /usr: not cur: No such file or directory > uptime: /dev//rently mounted > umount: /home: not currently : No such file or directory > uptime: /dev//mounted > umount: /dos: not currently mounted > : No such file or directory > 2:00AM up 6:08, 1 user, load averages: 1.28, 1.80, 1.74 > > > What is _that_??? > > I just cvsupped the latest sources. I'm going to do a make world when my > HD space will permit it, and I'll rebuild my kernel. We'll see then. > > Hoping that all this nightmare will end soon. > > On Thu, 8 Apr 1999, Eric Griff wrote: > > > Nope, hehe. > > > > I've probably built 50 kernels since my 'LINT' derived incident. Always in > > multi-user. > > > > One of the directives in the LINT configurations will do it. I suspect the > > Posix ones maybe. > > > > When I got that error (sorry for vaguenesses, but that was back at the end > > of February), rebuilding ps, had no effect either. But when I copied > > GENERIC, and added the other stuff I needed in, and installed it, after > > reboot, ps was fine again.. The problem actually seemed to arrise somehow > > out of PROCFS, as there were a few other things that didn't work right > > either. > > > > I haven't seen this since. I wish I had sent a bug report now.. It would > > have better memory than I do, hehe > > > > Eric A. Griff, > > NETDesign Inc. > > 181 Genesee St. > > Suite 500 > > Utica, NY 13501 > > (315) 734-1668 ext. 205 > > > > -----Original Message----- > > From: Spidey > > To: Tom > > Cc: freebsd-stable@freebsd.org > > Date: Thursday, April 08, 1999 7:59 PM > > Subject: Re: ps problems (explained) > > > > > > >I want to make clear for future generations that I recompiled my kernel > > >(several times!!!) after the 'installworld', so the problem is obviously > > >due to the fact that I did it in multi-user mode... > > > > > >naughty-naughty-naughty... :) > > > > > >On Thu, 8 Apr 1999, Tom wrote: > > > > > >> On Thu, 8 Apr 1999, Spidey wrote: > > >> > > >> > Hi! > > >> > > > >> > I've got serious problems with ps. I does not work at all: > > >> > > > >> > spidey@freed [03:01pm] spidey$ ps > > >> > ps: bad namelist > > >> > spidey@freed [03:01pm] spidey$ > > >> > > > >> > is all I can get. > > >> > > >> ... > > >> > Is it possible that a make world in multi-user mode caused this? > > >> > > >> Not as long as the version of "ps" matches the version of your kernel. > > >> > > >> > > >> Tom > > >> > > > > > >Si l'image donne l'illusion de savoir > > >C'est que l'adage pretend que pour croire, > > >L'important ne serait que de voir > > > > > > > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > > >with "unsubscribe freebsd-stable" in the body of the message > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > > Si l'image donne l'illusion de savoir > C'est que l'adage pretend que pour croire, > L'important ne serait que de voir > > Lofofora > > > Si l'image donne l'illusion de savoir C'est que l'adage pretend que pour croire, L'important ne serait que de voir Lofofora To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message