Re: Interrupted system calls

Article View: comp.unix.programmer

Article #253

Back to comp.unix.programmer Previous Next

#253

From: Dan Bernstein
Date: Mon, 06 Apr 1992 22:58

13 lines
1084 bytes

In article <JIK.92Apr6104609@pit-manager.mit.edu> jik@athena.mit.edu (Jonathan I. Kamens) writes:
> There are problems with just restarting in some cases.  For example, I
> believe it's possible for a write() to be interrupted after part of
> the data you give it has already been written, and I don't think
> there's any way to know how much data was written before the interrupt
> (ugh!).

On broken systems, and in stupid cases, yes. On working systems write()
will always return the number of bytes written, if that number is
positive. (Yes, this is part of my definition of ``working''; yes, there
exist systems which work in this respect.)

---Dan

Technical Details

Message-ID: <27851.Apr622.58.1392@virtualnews.nyu.edu>

Path: arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!uwm.edu!linac!att!ucbvax!virtualnews.nyu.edu!brnstnd

References: <1992Apr5.224334.24925@cc.uow.edu.au> <JIK.92Apr6104609@pit-manager.mit.edu>

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!uwm.edu!linac!att!ucbvax!virtualnews.nyu.edu!brnstnd
From: brnstnd@nyu.edu (Dan Bernstein)
Newsgroups: comp.unix.programmer
Subject: Re: Interrupted system calls
Message-ID: <27851.Apr622.58.1392@virtualnews.nyu.edu>
Date: 6 Apr 92 22:58:13 GMT
References: <1992Apr5.224334.24925@cc.uow.edu.au> <JIK.92Apr6104609@pit-manager.mit.edu>
Organization: IR
Lines: 13

Reply to Parent Message