No wild ideas but if I were in your shoes I'd put in some debugging
e.g change the rm -fr to a script that outputs timestamps , does a
stat for the file and file system, etc., etc., This coupled with pre
and post find timestamps might rule out/rule in certain potential
issues.
What kind of file system is /tmp mounted on? This could be some cache
related issue (seems strange though).
One wild idea - could the file name have non-printing characters i.e.
should that rm -rf {} be rm -rf "{}".
Paschal.
>> ---------- Forwarded message ----------
> From: Niall O Broin <niall at linux.ie>
> Subject: [ILUG] cron strangeness
.
>> find /tmp -name \*.incoming -mmin +1200 -exec rm -fr {} \;
>>> Any wild ideas?
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
