Subject: kern/21187: /proc & find: fts_read: No such file or directory
To: None <gnats-bugs@gnats.netbsd.org>
From: Hubert Feyrer <hubert@feyrer.de>
List: netbsd-bugs
Date: 04/15/2003 01:06:06
>Number: 21187
>Category: kern
>Synopsis: /proc & find: fts_read: No such file or directory
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: kern-bug-people
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Mon Apr 14 16:07:01 PDT 2003
>Closed-Date:
>Last-Modified:
>Originator: Hubert Feyrer
>Release: NetBSD 1.6R
>Organization:
bla!
>Environment:
System: NetBSD miyu 1.6R NetBSD 1.6R (MIYU) #14: Sat Apr 12 22:21:34 MEST 2003 feyrer@miyu:/usr/cvs/src-current/sys/arch/i386/compile/MIYU i386
Architecture: i386
Machine: i386
>Description:
when running find(1) on /proc or /emul/linux/proc (with -o linux),
find(1) aborts:
miyu# find /usr/pkg/emul/linux/proc -type f >/dev/null
find: fts_read: No such file or directory
miyu# find /proc -type f > /dev/null
find: fts_read: No such file or directory
This is annoying as the print-PLIST target in pkgsrc
prints incomplete PLISTs that way.
The real reason is suspected to lie within /proc, though.
>How-To-Repeat:
See above.
>Fix:
Unknown.
>Release-Note:
>Audit-Trail:
>Unformatted:
1.6R/i386 kernel with 1.6.1_RClatest userland