Xref: utzoo comp.unix.wizards:5883 comp.mail.misc:733 news.software.b:1041 Path: utzoo!mnetor!uunet!husc6!ukma!david From: david@ms.uky.edu (David Herron -- Resident E-mail Hack) Newsgroups: comp.unix.wizards,comp.mail.misc,news.software.b Subject: Re: Another way that news eats inodes Message-ID: <7958@e.ms.uky.edu> Date: 27 Dec 87 22:33:38 GMT References: <440@minya.UUCP> <375@octopus.UUCP> Reply-To: david@ms.uky.edu (David Herron -- Resident E-mail Hack) Organization: U of Kentucky, Mathematical Sciences Lines: 25 guys ... that /usr/spool/news/.rnews directory is controlled by the SPOOLNEWS code ... that is, if you have SPOOLNEWS defined then rnews will only put it's input into a file in the ".rnews" directory and exit quickly. The idea is to let uuxqt finish quickly with little chance of having lots of uuxqt's running at once. Later you run another program (in this case "rnews -U") to pick up the stuff in ".rnews" ... there's locking involved to make sure that only one "rnews -U" is running at a time... The *ONLY* time I've seen that method making zero length files is when the filesystem is out of free blocks. Oh ... another thing. If there are problems with a particular file, the SPOOLNEWS code moves the file to "/usr/spool/news" (er.. without making any kind of notification except for an errorlog entry). These comments are based on 2.11.8 ... I apologize if any details have changed since patch#8 but this last semester has been very very looooong. -- <---- David Herron -- The E-Mail guy <---- or: {rutgers,uunet,cbosgd}!ukma!david, david@UKMA.BITNET <---- <---- Winter health warning: Remember, don't eat the yellow snow!