Xref: utzoo comp.sys.att:6391 unix-pc.general:2872
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!gatech!emory!dtscp1!gbmatl!gbm
From: gbm@gbmatl.UUCP (gary mckenney)
Newsgroups: comp.sys.att,unix-pc.general
Subject: Re: Inode fixes & single user woes : was (3b1 40meg disk woes: Help)
Message-ID: <1762@gbmatl.UUCP>
Date: 7 May 89 17:46:58 GMT
References: <3961@emory.mathcs.emory.edu} <17513@cup.portal.com> <2947@ihuxy.ATT.COM> <586@cbnewsc.ATT.COM> <17733@cup.portal.com> <1989May5.150438.13740@ziebmef.uucp>
Reply-To: gbm@gbmatl.UUCP (Root)
Organization: Atlanta Programming & Consulting, Inc.
Lines: 22

In article <1989May5.150438.13740@ziebmef.uucp} cks@ziebmef.UUCP (Chris Siebenmann) writes:
}In article <17733@cup.portal.com> thad@cup.portal.com (Thad P Floryan) writes:
} Do these actually accumulate on the UNIX-PC? I try to keep my system
}up for as long as possible (the only problem I've found so far is that
}/etc/wmgr accumulates memory, so you have to kill and restart it every
}now and then), and after routine shutdowns and startups, fsck never
}seems to find any problems. Have people observed the infamous SysV
}disappearing-inodes problem on their machines? Are there other FS
}problems people have encountered?

I've run into the disappearing inode problem.  I shutdown to let fsck run
and it cleared the problem up.

I do have difficulty setting my machine to single user mode.
From the documentation the recommended way to do this is to type "init s".

On my machine this will successfully reboot the machine eventually but never
to quite make it into single user mode.

Any suggestions are appreciated.

gbm