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

Update of bug #51345 (project findutils): Assigned to: jay => None Fixed Release:None => 4.6.0 ___ Reply to this item at:

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

Update of bug #51345 (project findutils): Status:None => Fixed Assigned to:None => jay Open/Closed:Open => Closed

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

On Wednesday, July 05, 2017 16:01:53 James Youngman wrote: > Follow-up Comment #4, bug #51345 (project findutils): > > Try again, passing also the option -noleaf to find. The -noleaf option of find is silently ignored if find is built with FTS. I proposed a gnulib patch that would allow us to mak

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

Follow-up Comment #12, bug #51345 (project findutils): finutils4.6.0/find/oldfind also worked correctly for the test case I provided. ___ Reply to this item at:

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

Follow-up Comment #11, bug #51345 (project findutils): okay, that's good news - so the fix the Debian project needs is most probably somewhere in these 265 commits: $ git log --oneline FINDUTILS_4_4_2-1..v4.6.0 -- find lib | wc -l 265 To narrow it down even more, would you please check again

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

Follow-up Comment #10, bug #51345 (project findutils): I download latest version (4.6.0) of findutils source code and built the binaries from source. Then I did same tests and "find" command showed correct output for the first run. Then I downloaded findutils version 4.4.2 source code from gnu ar

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

Follow-up Comment #9, bug #51345 (project findutils): If you are only willing to use the binaries provided in your Linux distribution, then you should ask for support and help from that Linux distribution. The GNU project supports the "upstream" release - we release it as source code, not binarie

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

Follow-up Comment #8, bug #51345 (project findutils): I also asked about the same problem here: https://serverfault.com/questions/858747/linux-find-command-is-misbehaving Please take a look so I don't have to repeat all my comments here as well. __

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

Follow-up Comment #7, bug #51345 (project findutils): noleaf option doesn't make any difference. And yes as I said I repeat again all those files exist and are accessible from the beginning. I expected you to test this problem on a Debian with latest kernel to see whether it happens or not, sounds

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

Follow-up Comment #6, bug #51345 (project findutils): I don't want to sound like a crank, but are you verifying that the files in question actually exist before you run find? I mean, before you run find the first time, are you doing "ls /lib/systemd" to verify that the directory is accessible whe

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

Follow-up Comment #5, bug #51345 (project findutils): Oh, also try to compare the behaviour of "oldfind" which is built at the same time as "find", when you compile findutils from source (though your distribution likely does not ship it). __

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

Follow-up Comment #4, bug #51345 (project findutils): Try again, passing also the option -noleaf to find. If it works with -noleaf but not without it, one of the directories in the tree you searched has an incorrect[*] link count (i.e. st_nlink > 2 but not equal to 2 + the number of immediate chil

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

Follow-up Comment #3, bug #51345 (project findutils): Okay, so this happens after a fresh reboot. Thanks for the strace logs; but please compress them the next time because it was 12M+37M to download. If I got it right, then the last directory processed in the 1st run was /proc/sys/kernel/debu

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

Follow-up Comment #2, bug #51345 (project findutils): I thought the explanations should be enough. To clarify the problem I re-explain what happens: I turn on my Linux machine which has Debian 8 x64 (unstable- kernel 4.9) installed on it. I run the command > #find . -name "*systemd-resolved*" an

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

Follow-up Comment #1, bug #51345 (project findutils): This is strange, indeed. Furthermore, it would be good to have more information to reproduce the issue. To narrow things down, I suggest that you log the system calls into logfiles using "strace -v -o logfile find ...". Next, it is unclear to

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

URL: 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