cron help

[Pat Peter]

I have few cron entries that will process some scripts and redirect the output to a log file.

But since the log grows over time I would like to create a separate output for each day

ex-

current entry:

05,25 * * * * exec ksh -c '. ${HOME}/.profile;~/parse.sh >> /log/parse.log'

I would like to have

05,25 * * * * exec ksh -c '. ${HOME}/.profile;~/parse.sh > /log/parse.log_06022006'

Can anyone please help me.

-Pat

[john kingsley]

how about:

05,25 * * * * exec ksh -c '. ${HOME}/.profile;~/parse.sh > /log/parse.log_`date +%m%d%Y`'

[Darrel Louis]

Pat,

Don't forget to redirect with ">>", otherwise the file will be recreated every-time the cronjob starts.

05,25 * * * * exec ksh -c '. ${HOME}/.profile;~/parse.sh >> /log/parse.log_`date +%m%d%Y`'

Darrel

[Peter Nikitka]

Hi,

and even more - don't forget - as the previous poster, that a %-sign in a crontab-entry has a special meaning and must be escaped.
I think in HP-UX you have to write two percent signs:
05,25 * * * * exec ksh -c '. ${HOME}/.profile;~/parse.sh >> /log/parse.`date +%%m.%%d.%%y`.log

mfG Peter

[spex]

It might be cleaner to create and schedule a separate script to handle switching out of your parse.log, as well as other logfiles. Something like:

#!/usr/sbin/sh
DATE=`date +%Y%m%d`
cp /log/parse.log /log/parse.${DATE}.log
cat /dev/null > /log/parse.log

Have the script run just before midnight, so that the date in the filename matches the date of the log's contents.

PCS

[Doug O'Leary]

Hey;

Personally, I'd put the log inside the script:

Date=$(date +"%y%m%d")
Log=/log/parse_log_${Date}

(
commands to be executed
) >> ${Log} 2>&1

that way the crontab stays a little cleaner...

Doug