Path: utzoo!attcan!utgpu!watmath!att!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!uwm.edu!mailrus!purdue!haven!mimsy!mojo!eng.umd.edu!smaug
From: smaug@eng.umd.edu (Kurt Lidl)
Newsgroups: comp.unix.questions
Subject: Running out of inodes in /
Keywords: inodes, slash, tmp, bogus
Message-ID: <1989Sep21.205655.1098@eng.umd.edu>
Date: 21 Sep 89 20:56:55 GMT
Sender: news@eng.umd.edu (The C News System)
Reply-To: smaug@eng.umd.edu (Kurt Lidl)
Organization: Merriversity of Uniland, College Purgatory
Lines: 20


	Recently I tried to set the sticky bit on the /tmp directory
of a machine  here (a 3/60 running 4.0.1).  Within two days, the
machine crashed due to a shortage of inodes in the / partition.
Looking in the /tmp directory showed a huge collection of .getwdXXX
files, with the "XXX" being a pid, I assume.
	Sun claims that setting the sticky bit on a directory will
not allow anybody other than the owner to remove that file, regardless
of the permissions on the directory (even with rwxrwxrwx, only the
owner of the file could remove it).
	What I want to know is this just an implementation problem,
or is there more to the problem?  It seems that whatever is creating
the .getwdXXX files ought to clean up after itself a little better.
Any ideas on how to combat this problem?
	Any replies welcome (E-Mail preferred.)
--
==================================================================
==  Kurt J. Lidl  (smaug@hellcat.eng.umd.edu)	(301) 454-3184	==
==  UUCP: uunet!mimsy!smaug			(301) 454-1526	==
==========="X Windows: Power Tools for Power Fools"===============