Hi Folks

Thanks all for the quick replies and sorry for my late response. Healthwise 2018 isn't my year exactly....

Decided to follow RudiCs suggestion and switch to bash which works fine.

What we originally wanted to do : Put cronjobs into a wrapper script and use redirected outputs for centnalized logging, archiving, alarming

Details :
1. log : stderr only
Icinga (Nagios) will check for stderr log files. Log files individual for each cronjob.

2. log : stdout & stderr
Additionaly we'll create a local central log file - independet of what the individual cronjob logs or rather does not log.
All cronjobs of a server will log into that file, simultaniously.
As we got a lots of different cronjobs that (may) produce, or rather **** into stdout/stderr, that file will certainly become messy.
It's rather just for tail -f'ing if you're on the system and want to look at things going on.

3. log : stdout & stderr
We'll also archive sdtout & stderr - per single cronjob.


Wrapped crontab entry wil look like this


* 1 * * * WrapperScript.bash UniqueJobID Timeout OriginalCommand OriginalParameters



And yes, we looked at already available solutions but didn't find anything that wasn't over the top in size, complexity or cost for our limited purpose.

However, if you plan on doing something similar start here 8-) :
Job scheduler - Wikipedia

Thanks again all for your help!

Moderator's Comments:

Please use appropriate language as required by forum rules!