Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mira.net.au!inquo!in-news.erinet.com!izzy.net!aanews.merit.net!imci3!imci4!newsfeed.internetmci.com!news.mathworks.com!fu-berlin.de!cs.tu-berlin.de!informatik.uni-bremen.de!nordwest.pop.de!uniol!uni-erlangen.de!news.tu-chemnitz.de!irz401!uriah.heep!news
From: j@uriah.heep.sax.de (J Wunsch)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Bad file descriptor... What is this?
Date: 24 Apr 1996 22:24:38 GMT
Organization: Private FreeBSD site, Dresden
Lines: 25
Message-ID: <4lm9n6$s7o@uriah.heep.sax.de>
References: <317D17FC.167EB0E7@home.ifx.net>
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
NNTP-Posting-Host: localhost.heep.sax.de
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Newsreader: knews 0.9.6
"Robert L. Hatch" <rlhatch@home.ifx.net> writes:
>I am running FreeBSD 2.1-RELEASE. Upon restoring some files that were
>"tared", I can't do anything with some of the restored files.
EBADF (Bad file descriptor) is normally:
9 EBADF Bad file descriptor. A file descriptor argument was out of range,
referred to no open file, or a read (write) request was made to a
file that was only open for writing (reading).
(see errno(3)).
Some programs are stupid and issue this error message where it's not
appropriate.
There's another posting from you in the queue, and i think this will
get you further...
--
cheers, J"org
joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)