| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Named pipe defect in OS/2 3.0? |
Has anybody run into problems with interprocess named pipes failing to write and/or read any data or to read incorrect data out of pipes after OS/2 3.0 has been running for several hours or days? The problem I am having goes away if I reboot the system. Simply shutting down my processes and restarting them does not eliminate the problem once it has started happening. Thus I am more and more inclined to believe this is an OS/2 3.0 defect as this code was running reliably (at least the named pipes part) on OS/2 2.11. --- Maximus/2 2.01wb* Origin: OS/2 Connection {at} Mira Mesa, CA (1:202/354) SEEN-BY: 12/2442 54/54 620/243 624/50 632/348 640/820 690/660 711/409 410 413 SEEN-BY: 711/430 807 808 809 934 942 949 712/353 623 713/888 800/1 @PATH: 202/354 301 1 3615/50 229/2 12/2442 711/409 54/54 711/808 809 934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.