Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!lll-winken!sun-barr!newstop!texsun!letni!void!vector!holston!barton
From: barton@holston.UUCP (Barton A. Fisk)
Newsgroups: comp.unix.xenix
Subject: Re: EBADF when moving from Xenix to SCO Unix.
Summary: check permissions
Message-ID: <5751@holston.UUCP>
Date: 17 Aug 90 00:25:14 GMT
References: <1997@enea.se>
Organization: Barton A. Fisk & Co.
Lines: 18

In article <1997@enea.se>, mla@enea.se (Mats L|fstr|m) writes:
> 
> On the Xenix system, the application work just fine, but when running
> the same basic programs on SCO Unix, they frequently gets EBADF when
> trying to write files.
> 
> Questions are:
> - Has anyone seen this before?
> - What to do about it?

Check the permissions on the files, EBADF means bad file number.
Either a file descripter refers to no open file or a read request
was made to a write only file or vice versa.

Hope this helps.
Bart
-- 
uucp: holston!barton