Thread View: comp.sys.concurrent
1 messages
1 total messages
Started by Paul Asmar
Sun, 27 Jan 1991 20:23
write system call
Author: Paul Asmar
Date: Sun, 27 Jan 1991 20:23
Date: Sun, 27 Jan 1991 20:23
26 lines
1505 bytes
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
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads