Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ihnp4!cuae2!ltuxa!ttrdc!levy
From: levy@ttrdc.UUCP
Newsgroups: comp.sources.bugs
Subject: Re: RN 4.3 (patch level 43(?))
Message-ID: <1764@ttrdc.UUCP>
Date: Mon, 15-Jun-87 18:48:42 EDT
Article-I.D.: ttrdc.1764
Posted: Mon Jun 15 18:48:42 1987
Date-Received: Wed, 17-Jun-87 02:19:21 EDT
References: <952@ncsuvx.ncsu.edu> <1074@rayssd.RAY.COM>
Organization: AT&T, Skokie, IL
Lines: 23

In article <1074@rayssd.RAY.COM>, dhb@rayssd.RAY.COM (David Brierley) writes:
< In article <952@ncsuvx.ncsu.edu> abc@ncsuvx.ncsu.edu (Alan B. Clegg) writes:
< >When a user goes over disk quota while reading news with RN, there is a good
< >chance that RN will destroy the users $HOME/.newsrc file, leaving it zero 
< >length.
< >
< >Any fixes for this one?
< 
< This is not an RN problem but a generic UNIX problem.  Any program which
< opens a file for output is subject to leaving a zero length file when the
< user goes over quota.  Either that or vi,ex,ed,emacs,cc (too name a few)
< all have the same identical bug that rn has!!

This kind of problem could be avoided by opening a temp file in the same
directory as the .newsrc file (if possible), writing the new .newsrc data
into it, and if the write was successful unlinking the old .newsrc, linking the
new file to .newsrc, then unlinking the original temporary file name.
It would be an additional "friendly" feature.
-- 
|------------dan levy------------|  Path: ..!{akgua,homxb,ihnp4,ltuxa,mvuxa,
|         an engihacker @        |		vax135}!ttrdc!ttrda!levy
|    at&t data systems division  |  Disclaimer:  try datclaimer.
|--------skokie, illinois--------|