Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!mit-eddie!uw-beaver!tektronix!reed!psu-cs!curnutt
From: curnutt@psu-cs.UUCP
Newsgroups: comp.unix.xenix
Subject: ENOTTY sometimes spurious
Message-ID: <415@psu-cs.UUCP>
Date: Thu, 16-Apr-87 13:08:48 EST
Article-I.D.: psu-cs.415
Posted: Thu Apr 16 13:08:48 1987
Date-Received: Sat, 18-Apr-87 03:49:17 EST
References: <143@sds.UUCP>
Reply-To: curnutt@psu-cs.UUCP (Bryan Curnutt)
Organization: Dept. of Computer Science, Portland State University; Portland OR
Lines: 22

Other Organization: Store Systems Information,  Portland, Oregon
Keywords: 


In article <143@sds.UUCP> dave@sds.UUCP (dave schmidt x194) writes:
>
>I just found a nasty problem with lex on Microsoft XENIX System V; 
>
                     .
  [description of lex input() sometimes failing with error ENOTTY ]
  [(Not a typewriter)]
                     .
>Has anyone seen or heard of anything similiar?


We're using SCO Xenix on a Sperry IT, and I've found that fprint(),
when used with text files, will always set errno to ENOTTY and return
a non-zero value.  What makes this more interesting is that the
fprintf() DOES WORK.  I called SCO about this, and they told me
to ignore it.

Bryan "Well, it's better than DOS" Curnutt