Path: utzoo!attcan!uunet!world!decwrl!wuarchive!emory!gatech!prism!gt0178a
From: gt0178a@prism.gatech.EDU (Jim Burns)
Newsgroups: comp.unix.internals
Subject: Re: On the silliness of close() giving EDQUOT
Message-ID: <15544@hydra.gatech.EDU>
Date: 20 Oct 90 10:03:05 GMT
References: <BZS.90Oct19233255@world.std.com>
Organization: Georgia Institute of Technology
Lines: 19

in article <BZS.90Oct19233255@world.std.com>, bzs@world.std.com (Barry Shein) says:

> OS/360/370 interrupted (signal) when there was an I/O error
> (SYNAD=handler) of any sort and you could pick apart what happened in
> the handler() routine.

> The only hard part was knowing where your program was when the error
> struck.

And what do you do if the I/O is done as the result of a close? And worse,
if the close is a result of exit processing, and the process doesn't exist
anymore to get the interrupt? Without timely notification, it's hard to
recover.

-- 
BURNS,JIM
Georgia Institute of Technology, Box 30178, Atlanta Georgia, 30332
uucp:	  ...!{decvax,hplabs,ncar,purdue,rutgers}!gatech!prism!gt0178a
Internet: gt0178a@prism.gatech.edu