paul@cosmo.Jpl.Nasa.Gov (Paul Asmar) (01/28/91)
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