> On Sat, Oct 06, 2007 at 10:25:09AM -0400, [EMAIL PROTECTED]
> com wrote:
> > Just to confirm that this bug still exists...
>
> It looks like you have some crontab entries which trigger this bug, could
> you please run=20
>
> sh -x /usr/lib/tiger/scripts/check_crontabs 2>&1=20
>
> And send me the output?
Better yet, I'll tell you the bug. (Once I looked at the output,
it became obvious.)
I used a vixie-cron extension, namely the "@daily" interval.
@daily find $dir1 -mtime +14 -exec rm {} \; ; find $dir2 -mmin +10 -exec rm {}
\; ;
This, of course, mucks up tiger's crontab parsing. It's skipping the
first 5 fields and invoking "basename -exec", which is causing the
problems.
+ read owner command
++ /bin/sed -e 's/[0-9]*>//g'
++ echo '-exec rm {} ; ; find $dir2 -mmin +10 -exec rm {} ; ;'
++ /usr/bin/tr -d '()\;`&!|'
+ com='-exec rm {} find $dir2 -mmin +10 -exec rm {} '
++ echo '-exec rm {} find $dir2 -mmin +10 -exec rm {} '
++ /usr/bin/awk '{print $1}'
+ cmd=-exec
++ /usr/bin/basename -exec
/usr/bin/basename: invalid option -- e
Try `/usr/bin/basename --help' for more information.
The workaround is obvious (expand @daily per the man page), but perhaps
adding support for the extension would be a feature request?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
