Your message dated Sat, 12 Nov 2016 18:24:00 +0100 with message-id <[email protected]> and subject line Re: Bug#842560: findutils: find fails to recurse from / downwards on first invocation after boot has caused the Debian Bug report #842560, regarding findutils: find fails to recurse from / downwards on first invocation after boot to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 842560: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842560 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: findutils Version: 4.4.2-9+b1 Severity: important Dear Maintainer, find doesn't find on first invocation, only on second and subsequent ones after a boot. * What led up to the situation? Fresh boot, then log in as root. * What exactly did you do (or not do) that was effective (or ineffective)? Invoked the find command twice within seconds of each other. The first invocation does not recurse down from the root of the file system except for entering /sys/ The second and every subsequent invocation will recurse properly. Example output: root@host:~# find / -iname 'cpufrequtils*' /sys/fs/cgroup/devices/system.slice/cpufrequtils.service /sys/fs/cgroup/systemd/system.slice/cpufrequtils.service root@host:~# find / -iname 'cpufrequtils*' /sys/fs/cgroup/devices/system.slice/cpufrequtils.service /sys/fs/cgroup/systemd/system.slice/cpufrequtils.service /run/systemd/generator.late/runlevel5.target.wants/cpufrequtils.service /run/systemd/generator.late/runlevel4.target.wants/cpufrequtils.service /run/systemd/generator.late/runlevel3.target.wants/cpufrequtils.service /run/systemd/generator.late/runlevel2.target.wants/cpufrequtils.service /run/systemd/generator.late/cpufrequtils.service /usr/share/lintian/overrides/cpufrequtils /usr/share/doc/cpufrequtils /usr/share/doc/cpufrequtils/examples/cpufrequtils.sample /usr/share/doc/cpufrequtils/examples/cpufrequtils.loadcpufreq.sample /usr/share/locale/pt/LC_MESSAGES/cpufrequtils.mo /usr/share/locale/it/LC_MESSAGES/cpufrequtils.mo /usr/share/locale/ca/LC_MESSAGES/cpufrequtils.mo /usr/share/locale/fr/LC_MESSAGES/cpufrequtils.mo /usr/share/locale/cs/LC_MESSAGES/cpufrequtils.mo /usr/share/locale/de/LC_MESSAGES/cpufrequtils.mo /etc/init.d/cpufrequtils /var/lib/dpkg/info/cpufrequtils.prerm /var/lib/dpkg/info/cpufrequtils.templates /var/lib/dpkg/info/cpufrequtils.list /var/lib/dpkg/info/cpufrequtils.conffiles /var/lib/dpkg/info/cpufrequtils.postinst /var/lib/dpkg/info/cpufrequtils.md5sums /var/lib/dpkg/info/cpufrequtils.postrm * What was the outcome of this action? First invocatoin of find did not actually find what it should find. * What outcome did you expect instead? Output as shown by the second invocation (see above) -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.5.0-0.bpo.1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages findutils depends on: ii libc6 2.19-18+deb8u4 findutils recommends no packages. Versions of packages findutils suggests: ii mlocate 0.26-1 -- no debconf information
--- End Message ---
--- Begin Message ---Version: 4.6.0-1 On 2016-11-03 [email protected] wrote: > Von: "Andreas Metzler" <[email protected]> [...] >> That looks pretty much identical to >> https://savannah.gnu.org/bugs/?47261[https://savannah.gnu.org/bugs/?47261] >> Could you check whether it is also fixed with the latest release? > Had to build from source at > http://ftp.gnu.org/gnu/findutils/findutils-4.6.0.tar.gz because > version 4.6.0+git+20160703-2 from the stretch repo won't install on > jessie. The good news is that, yes, version 4.6.0 from the gnu repo > did fix it. Thanks, marking as fixed in 4.6.0-1. > Can I suggest that an installable flavour of 4.6.0 is > made available in jessie-backports at least (jessie main would be even > better)? That is not feasible. find dropped the '-perm +xyz' syntax and multiple packages in jessie use this (e.g. python). cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
--- End Message ---
