Hi,

dpkg -s findutils will probably show the file as orphaned
configuration file. - It was dropped in 4.2.31-2.

Thank for your fast answer. I will try to do my best ;-)

It should not there. It should have been automatically removed or renamed
when you upgraded findutils from version older than 4.2.31-2 to a newer
one.

This error message looks fishy. Do you see this on on 'dpkg -s
findutils`, too? What do
md5sum /etc/cron.daily/find
dpkg-query -W -f='${Conffiles}' findutils
say?

dpkg -s findutils

Package: findutils
Essential: yes
Status: install ok installed
Priority: required
Section: utils
Installed-Size: 1704
Maintainer: Andreas Metzler <[email protected]>
Architecture: i386
Source: findutils (4.4.2-1)
Version: 4.4.2-1+b1
Depends: dpkg (>= 1.15.4) | install-info
Pre-Depends: libc6 (>= 2.4)
Suggests: mlocate | locate | slocate
Conffiles:
 /etc/cron.daily/find 7eb265877a0e861849027c1f6ec8e8ec obsolete
Description: utilities for finding files--find, xargs

md5sum /etc/cron.daily/find*

7eb265877a0e861849027c1f6ec8e8ec  /etc/cron.daily/find
7eb265877a0e861849027c1f6ec8e8ec  /etc/cron.daily/find.notslocate.dpkg-new

dpkg-query -W -f='${Conffiles}' findutils

 /etc/cron.daily/find 7eb265877a0e861849027c1f6ec8e8ec obsolete

The unique problem is that script do nothing but finish with code error 127 so I get a cron mail * number of computer... Because I do not have so many time, I do not take the time before to go ahead...

It's very easy for me to remove this file by cfengine on all ours computers. This report is more to understand why and when this arrive...

Under lenny, I used slocate which is not any more in squeeze. Under squeeze, I remove all possible locate... Some computers cames even from sarge !

Thanks

gaby
--
Gabriel Moreau - IR CNRS                http://www.legi.grenoble-inp.fr
LEGI (UMR 5519) Laboratoire des Ecoulements Geophysiques et Industriels
BP53, 38041 Grenoble Cedex, France                  tel:+33.476.825.015
mailto:[email protected]                   fax:++.271


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to