Hi,

I have two daily cronjobs for SquidAnalyzer and Squid log rotation. I'd like to combine them, and I wonder what's the best solution for this.

Every day at 13:00 I'm running /usr/bin/squid-analyzer. This command parses /var/log/squid/access.log and generates a detailed report about web usage. On some machines with many clients, this command can run for several minutes.

Next thing I have to do is run another cronjob for /usr/sbin/squid -k rotate, to rotate Squid's log files. Again, on networks with many clients, /var/log/squid/access.log* can get quite huge, so rotating the logs is vital to keep things manageable.

What would be the syntax to execute one cronjob after another? Can I simply put the following in a cronjob?

Cheers,

Niki

Why not write a script that calls the two commands, one after the other, and then you schedule the script as a cron job?

1 members found this post helpful.

Why not logrotate . It's just for logs.

Sample:


or if it,s important at specific time of the day different from cron.daily do this by cron job:

it's only for squid log not affects regular logrogate job.

2 members found this post helpful.

++ What BradPit said.

It will work, or if you want run squid -k rotate anyway after, could be '/usr/bin/squid-analyzer;/usr/sbin/squid -k rotate'

That command will run the second half only if the first command succeeds. If, for some reason, squid-analyzer bombs out and throws an exit code other than 0 (0 means a successful exit without errors), your logs won't rotate. If you want both commands to run no matter what, you'd want to do one of the following: replace the && with a ; (semicolon), create a shell script with them either on separate lines (as Eric mentioned), or separate them into separate cron jobs (which could entail using logrotate as BratPit mentioned).

See this stackexchange answer to see the differences between && || and ;

1 members found this post helpful.

See crontab(1) - jobs can be made to depend on other jobs. I've never used this functionality, but I've run across it several times in the manual page and filed it away as something that could be useful at some point. Here we are. :-)

2 members found this post helpful.

Thanks for your numerous answers, guys. For some reason, I've found out that SquidAnalyzer simply stopped working, and I have this problem to tackle first before giving the above suggestions a try.

Cheers,

Niki