[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #37811] Mismatch of messages given by `find --help' and its real ex

From: James Youngman
Subject: [bug #37811] Mismatch of messages given by `find --help' and its real execution result.
Date: Sun, 25 Nov 2012 14:12:09 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.11 (KHTML, like Gecko) Chrome/23.0.1271.64 Safari/537.11

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:

          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
                     -follow option is in effect, unless the symbolic link 
                     broken.  If you want to search for symbolic links when
                     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:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]