brianw@hpausla.HP.COM (Brian Wallis) (03/28/89)
Does anyone know of errors in the pipe() implementation in SCO Xenix 386 V 2.2.3. I have a friend trying to get the ACSnet software (this is the news/mail networking software of choice in Australia) to work reliably on his 386AT and there seems to be some problem with pipes. The problem manifests itself in that some of the data written to the pipe is being read twice by the reading process. The writing process writes words (ascii) seperated by spaces followed by a NULL to signify end of message. The reading process reads single characters up to a NULL and then processes the message. (This is the interface between NNcall and it's modem dialing program) The writes and reads are done using write(2) and read(2). The occurence of the bug is random. The software is compiled without optimization. Ring any bells with anyone? Any help will save my friends sanity. (and after the obscure cron bug, he hasn't much of that left!)