Path: utzoo!attcan!telly!lethe!torsqnt!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!ginosko!uunet!crdgw1!crdos1!davidsen
From: davidsen@crdos1.crd.ge.COM (Wm E Davidsen Jr)
Newsgroups: comp.unix.questions
Subject: Re: Running out of inodes in /
Keywords: inodes, slash, tmp, bogus
Message-ID: <455@crdos1.crd.ge.COM>
Date: 22 Sep 89 12:30:44 GMT
References: <1989Sep21.205655.1098@eng.umd.edu>
Reply-To: davidsen@crdos1.UUCP (bill davidsen)
Organization: GE Corp R&D Center
Lines: 11

It seems obvious that since you didn't previously have this problem,
whatever creates those files in tmp *is* trying to clean up after
itself. For some reason the UID of the creating and deleting processes
are not the same. You should find out what's happening, then either run
something setuid, run a cleanup as root, or turn the bit back off.

-- 
bill davidsen	(davidsen@crdos1.crd.GE.COM -or- uunet!crdgw1!crdos1!davidsen)
"The world is filled with fools. They blindly follow their so-called
'reason' in the face of the church and common sense. Any fool can see
that the world is flat!" - anon