🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: gnu.emacs.bug
Article #1678

emacs 18.54 close bug

#1678
From: rusty
Date: Wed, 10 May 1989 19:20
13 lines
1104 bytes
In the Usenet newsgroup comp.protocols.nfs someone from Sun gave a
long explanation about soft versus hard nfs mounts and using the
"intr" option with hard mounts.  In their explanation they also
pointed out how on an nfs mount a write() may fail but you may not get
the notification until you do a close().

Out of curiosity I looked at the code in fileio.c and in write-region
it does check the return value of close() but there are other places
where it doesn't, for example in copy-file it doesn't check the return
status when closing the output file descriptor.  I think someone
should eyeball the code carefully and check all of the close calls and
have it check the return status on the ones that are output file
descriptors.
Technical Details
Message-ID: <8905101920.AA28497@garnet.berkeley.edu>
Path: arc1-ca.pugleaf.net!utzoo!utgpu!watmath!uunet!tut.cis.ohio-state.edu!ucbvax!GARNET.BERKELEY.EDU!rusty

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!watmath!uunet!tut.cis.ohio-state.edu!ucbvax!GARNET.BERKELEY.EDU!rusty
From: rusty@GARNET.BERKELEY.EDU
Newsgroups: gnu.emacs.bug
Subject: emacs 18.54 close bug
Message-ID: <8905101920.AA28497@garnet.berkeley.edu>
Date: 10 May 89 19:20:56 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: Computer Center, UC Berkeley
Lines: 13