Update of bug #37811 (project findutils):
Status: None => Invalid
Assigned to: None => jay
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #1:
No need to read the source code, you could just read the documentation - it's
a platform-specific feature.
>From the full documentation:
2.5 Type
========
-- Test: -type c
True if the file is of type C:
...
`D'
door (Solaris)
Also the manual page:
-type c
File is of type c:
b block (buffered) special
c character (unbuffered) special
d directory
p named pipe (FIFO)
f regular file
l symbolic link; this is never true if the -L option or
the
-follow option is in effect, unless the symbolic link
is
broken. If you want to search for symbolic links when
-L
is in effect, use -xtype.
s socket
D door (Solaris)
While it's reasonable for "-type D" to fail on systems where Doors don't
exist, it's safer not to do that I think. I'm considering for example the
case where an old version of find runs against a new file system; -type D
should not fail on files that really are Doors, simply because it can't
recognise them. The fatal exit signals that find doesn't think it can
reliably recognise a Door file.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?37811>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
