|
-
September 23rd, 2006, 07:24 PM
#1
Semaphore timeout while using pipes?
I'm using named pipes two communicate between two processes on the same computer. Quite frequently (and randomly), however, a ConnectNamedPipe() operation fails and GetLastError() returns 121, which according to MSDN is due to a semaphore timeout. Can someone explain what pipes have to do with semaphores and why I could be getting this error?
EDIT: Sorry, I made a mistake. It is CreateFile(), not ConnectNamedPipe(), that produces the error.
Last edited by HighCommander4; September 25th, 2006 at 05:53 PM.
Old Unix programmers never die, they just mv to /dev/null
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|