From: Green, Simon (Simon.Green@EU.ALTRIA.COM)
Date: Tue May 27 2003 - 11:11:49 EDT
Life is much simpler if you put that sort of thing into a script. That way
it's easier to get a valid test and you don't need to make as many changes
to crontab. You can also take care of output redirection, environment
variables and the like within the script. I'd start by doing that and
testing it again.
Simon Green
Altria ITSC Europe s.a.r.l.
AIX-L Archive at http://marc.theaimsgroup.com/?l=aix-l&r=1&w=2
AIX FAQ at http://www.faqs.org/faqs/aix-faq/
N.B. Unsolicited email from vendors will not be appreciated.
> -----Original Message-----
> From: Shawn Bierman [mailto:BiermanS@METHODISTHEALTH.ORG]
> Sent: 27 May 2003 14:55
> To: aix-l@Princeton.EDU
> Subject: bad 'find' job in cron
>
>
> Greetings,
>
> I have a job in cron that works fine from the command line
> but when the cron job runs i get the following email:
>
> find: 0652-009 There is a missing conjunction
>
>
> *****************************************************************
> cron: The previous message is the standard output
> and standard error of one of the cron commands.
>
> The cron entry looks like this:
> 15 02 * * * (/usr/bin/find /sapbc/Server/logs -name \*.log
> -mtime +30 -xdev -type f | /usr/bin/xargs rm -f)
> 20 02 * * * (/usr/bin/find /sapbc/Server/packages/SAP/logs
> -name \*.log -mtime +30 -xdev -type f | /usr/bin/xargs rm -f)
>
>
> Ran from the command line it works fine. What does cron not
> like here?
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 22:16:52 EDT