home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.unix.programmer:4480 comp.unix.wizards:3731
- Newsgroups: comp.unix.programmer,comp.unix.wizards
- Path: sparky!uunet!europa.asd.contel.com!darwin.sura.net!jvnc.net!yale.edu!yale!gumby!destroyer!caen!umeecs!umn.edu!math.fu-berlin.de!unidui!flyer!flatlin!bad
- From: bad@flatlin.ka.sub.org (Christoph Badura)
- Subject: Re: STREAMS M_ERROR Message problem
- Organization: Guru Systems/Funware Department
- Date: Fri, 28 Aug 1992 09:53:37 GMT
- Message-ID: <Btou5D.6DH@flatlin.ka.sub.org>
- References: <1992Aug26.130739.19300@usenet.ins.cwru.edu>
- Lines: 12
-
- In <1992Aug26.130739.19300@usenet.ins.cwru.edu> am815@cleveland.Freenet.Edu (Joel Peter Anderson) writes:
- >The result is the next read or write returns with a -1 and errno is
- >set to 256 - status_code. The PROBLEM is that the only way to
- >clear the error condition is to close the device. Typically, the
- >error does not warrent a close.
-
- The *ONLY* way to clear the error condition caused by a M_ERROR
- message is to close the stream. It's documented that way.
- --
- Christoph Badura --- bad@flatlin.ka.sub.org
-
- ISO? Nicht immer, aber immer M-vfter.
-