write system call

Article View: comp.sys.concurrent

Article #76

Back to comp.sys.concurrent Previous Next

#76

From: Paul Asmar
Date: Sun, 27 Jan 1991 20:23

26 lines
1505 bytes

I am having problems with the write(2) system call on RTU 5.0.  When
I write a block of data across a pipe or a socket and a signal comes, write
returns -1 and writes some of the data.  I can't tell how much of the data has
already been transmitted, because write doesn't return it.

If write is interrupted and some of the data has been written, write
is supposed to return how much data has been written and *not* -1.  That
seems to a bug in Concurrent's implementation of that Unix system call.

Can someone please respond on this one soon?  Because I am really stuck.  I
am stuck even more because I can't use your sigblock() because it doesn't
save signals when they are blocked, which sigblock() is supposed to.


					Paul

-- 
--
Paul Asmar 	(paul@elroy.jpl.nasa.gov)
Jet Propulsion Laboratory
Pasadena, CA

Articles to: concurrent@soma.bcm.tmc.edu or uunet!soma.bcm.tmc.edu!concurrent
Administrative stuff: concurrent-request@soma.bcm.tmc.edu
Stan Barber, Moderator

Technical Details

Message-ID: <3768@gazette.bcm.tmc.edu>

Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!bcm!soma!concurrent-request

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!bcm!soma!concurrent-request
From: paul@cosmo.Jpl.Nasa.Gov (Paul Asmar)
Newsgroups: comp.sys.concurrent
Subject: write system call
Keywords: signals
Message-ID: <3768@gazette.bcm.tmc.edu>
Date: 27 Jan 91 20:23:07 GMT
Sender: usenet@bcm.tmc.edu
Organization: Image Analysis Systems Group, JPL
Lines: 26
Approved: concurrent@soma.neusc.bcm.tmc.edu
Nntp-Posting-Host: cortex.neusc.bcm.tmc.edu
Nntp-Posting-Host: cosmo.jpl.nasa.gov