Mail Archives: cygwin/2001/08/28/11:22:12
Just to remove a silly possibility, you didn't perchance run this from the
shell, see it remove files, then immediately schedule it as a cron job, and
see that the cron job didn't remove any files, did you?
If so, I think you'l see the same behavior if you run it from the shell
again. You already removed all the files less than 4 days old. Running it
again immediately after won't find anything else.
If that's not the case, then I don't know what the problem could be.
-----Original Message-----
From: James Nallen [mailto:James DOT Nallen AT may DOT ie]
Sent: Tuesday, August 28, 2001 4:16 AM
To: cygwin AT cygwin DOT com
Subject: unexpected behaviour of 'find' command
Hi,
I'm running cygwin-1.3.2, setup-2.78.2.3 on w2k pro in stand-alone mode.
The following file,
-rwxr-xr-x 1 Administ None 154 Aug 28 11:43 del_oldfiles.out
contains
#! /bin/sh
rm -f '/home/Administrator/oldfiles.txt'
/usr/bin/find.exe /e/work/DBA_Scripts -depth -type f -mtime -4 -exec rm -f
{} \;
date >> oldfiles.txt
When this file is executed from the command shell, it executes as expected.
When it is executed from a Cron job, the find command seems to do nothing.
Anyone know why this is so?
Regards,
James Nallen,
NUI Maynooth,
Co. Kildare,
Ireland.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -