Date: Mon, 11 Nov 2002 10:22:29 -0800 (PST) From: Noah Garrett Wallach <sleek@enabled.com> To: freebsd-questions@freebsd.org Subject: troubleshoot: Bad file descriptors Message-ID: <20021111101951.E96450-100000@typhoon.enabled.com>
next in thread | raw e-mail | index | archive | help
I am wanting to know how to troubleshoot the Bad File Descriptors that are creeping in when I am ls and find files. How can I stop this from happening? I dont see any open bugs at this time? Is my drive possibly bad? ---- snip ---- find: /usr/ports/korean.old/hanterm/files: Bad file descriptor find: /usr/ports/korean.old/gaim: Bad file descriptor find: /usr/ports/korean.old/kde3-i18n: Bad file descriptor find: /usr/ports/korean.old/ghostscript-gnu-korfont: Bad file descriptor find: /usr/ports/korean.old/openoffice: Bad file descriptor find: /usr/ports/java.old/linux-blackdown-jdk12/files: Bad file descriptor find: /usr/ports/java.old/linux-sun-jdk13: Bad file descriptor find: /usr/ports/java.old/linux-sun-jdk14: Bad file descriptor find: /usr/ports/java.old/java-checkstyle: Bad file descriptor find: /usr/ports/java.old/jakarta-log4j: Bad file descriptor find: /usr/ports/java.old/jakarta-commons-collections: Bad file descriptor find: /usr/ports/java.old/jakarta-commons-lang: Bad file descriptor find: /usr/obj/usr/src/gnu/usr.bin/perl/suidperl/lib/auto: Bad file descriptor find: /usr/obj/usr/src/gnu/usr.bin/perl/suidperl/build: Bad file descriptor ---- snip ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021111101951.E96450-100000>