bug-findutils
[Top][All Lists]
Advanced

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

[bug #51345] find shows different results despite using same command


From: anonymous
Subject: [bug #51345] find shows different results despite using same command
Date: Fri, 30 Jun 2017 03:45:47 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0

URL:
  <http://savannah.gnu.org/bugs/?51345>

                 Summary: find shows different results despite using same
command
                 Project: findutils
            Submitted by: None
            Submitted on: Fri 30 Jun 2017 07:45:45 AM UTC
                Category: find
                Severity: 3 - Normal
              Item Group: Wrong result
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: CyrusSh
        Originator Email: address@hidden
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 4.4.2
           Fixed Release: None

    _______________________________________________________

Details:

During working on terminal I came to see a very strange behavior from find
command. This is the command I run along with its output:

address@hidden:/# find . -name "*systemd-resolved*"
./usr/share/man/man8/systemd-resolved.service.8.gz
./usr/share/man/man8/systemd-resolved.8.gz

The command returns 0 or two results like above. But if I run the command the
second time I get:

address@hidden:/# find . -name "*systemd-resolved*"
./usr/share/man/man8/systemd-resolved.service.8.gz
./usr/share/man/man8/systemd-resolved.8.gz
./lib/systemd/systemd-resolved
./lib/systemd/system/systemd-resolved.service.d
./lib/systemd/system/systemd-resolved.service

This means the first time, "find" does not actually find everything. Also this
only happens one time. Running the command next times shows correct output. I
checked this on some other systems with Debian OS installed. On those with
Kernel 4.9+ this exact problem always occurs but on systems with kernel 3.16
it doesn't happen.




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?51345>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

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