[Top][All Lists]

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

[bug #20688] 'find / -nowarn -maxdepth 0 -name /' still warns

From: Eric Blake
Subject: [bug #20688] 'find / -nowarn -maxdepth 0 -name /' still warns
Date: Sat, 04 Aug 2007 21:29:19 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20070725 Firefox/ Mnenhy/


                 Summary: 'find / -nowarn -maxdepth 0 -name /' still warns
                 Project: findutils
            Submitted by: ericb
            Submitted on: Saturday 08/04/2007 at 15:29
                Category: find
                Severity: 3 - Normal
              Item Group: Wrong result
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: Eric Blake
        Originator Email: address@hidden
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 4.2.21
           Fixed Release: None



The warning issued by -name when the pattern includes '/' is not mentioned in
find.texi, either as a suppressable warning or as a severe warning.  I think
it should be suppressable, because as the following command line shows, it is
only a warning and not a hard fact that -name / usually results in no

$ find / -nowarn -maxdepth 0 -name /
find: warning: Unix filenames usually don't contain slashes (though pathnames
do).  That means that '-name `/'' will probably evaluate to false all the time
on this system.  You might find the '-wholename' test more useful, or perhaps
'-samefile'.  Alternatively, if you are using GNU grep, you could use 'find
... -print0 | grep -FzZ `/''.

Either way, whether we change parser.c to let -nowarn suppress this warning
or not, we also need to document this warning in find.texi.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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