🚀 go-pugleaf

Relay-Version: VMS News - V5.9C 19/12/89 VAX/VMS V5.3; site vax1.cc.lehigh.edu
Path: vax1.cc.lehigh.edu!vax1.cc.lehigh.edu!netnews.upenn.edu!rutgers!tut.cis.ohio-state.edu!BUCSF.BU.EDU!jbw
Newsgroups: gnu.emacs.bug
Subject: Is bug with not checking return status close() fixed yet?
Message-ID: <9010190335.AA03187@bucsf.bu.edu>
From: jbw@BUCSF.BU.EDU (Joe Wells)
Date: 19 Oct 90 03:35:22 GMT
Sender: daemon@tut.cis.ohio-state.edu
Distribution: gnu
Organization: GNUs Not Usenet
Approved: bug-gnu-emacs@prep.ai.mit.edu
Lines: 21

I'm wondering if the bug described here has been fixed:

  Jonathan I. Kamens <jik@athena.mit.edu> writes:

    If you are working on a remote filesystem (such as NFS or AFS), your
  file is often not completely flushed to the remote filesystem until you
  close it.  Therefore, if you are (for example) close to your quota, and
  you do close(), it is quite possible that the close() will put you over
  your quota and therefore fail.

    However, programmers who don't check close() never find out that the
  file didn't get written because the user went over his quota, and this
  can have very bad effects, for example, GNU emacs 18.54 (I don't know
  about 18.55, we haven't switched to it yet) didn't check close() when
  saving files, so a user might spend several hours working on a paper,
  then save it (without getting any errors from emacs) and log out.  The
  next time he logs in, the paper is empty, and all his work has been
  lost.

-- 
Joe Wells <jbw@bu.edu>