troubleshoot: Bad file descriptors
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 [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: troubleshoot: Bad file descriptors
--- more to the story --- did fsck in single user mode. even rebuilt the OS and kernel and installed it all. What else can I do? - Noah --- more to the story --- On Mon, 11 Nov 2002, Noah Garrett Wallach wrote: > > > 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 [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: troubleshoot: Bad file descriptors
Hi, It was also mentioned that there might be a bug with find. is this the case? I cannot seem to find anything with a gnats search. Figured I would at least ask to end this possibility --- snip --- FreeBSD blah.com 4.7-STABLE FreeBSD 4.7-STABLE #0: Thu Nov 7 16:18:33 PST 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/LOCAL i386 --- snip --- On Mon, 11 Nov 2002, Noah Garrett Wallach wrote: > > > --- more to the story --- > > did fsck in single user mode. even rebuilt the OS and kernel and > installed it all. What else can I do? > > - Noah > > --- more to the story --- > > On Mon, 11 Nov 2002, Noah Garrett Wallach wrote: > > > > > > > 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 [EMAIL PROTECTED] > > with "unsubscribe freebsd-questions" in the body of the message > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
