Description

#Introduction

Default Unix and linux cronjobs are quite basic stuff. Mostly you create “simple, stupid” jobs without output … that just run. Or should.

If you use a cronjob you need to hide the output otherwise the root user gets an email. So if you generate the output and have many cronjobs then you need a convention how to name your log files.

Questions:

• How do you check if a job was successful? Just trust them? Watching each log? On each of your systems?
• How do you detect if the last job execution was successful but does not run anymore?

My simple approach:

By just adding a wrapper in front of your current command breaks tons of limits! Suddenly a simple action opens so many possibilities.

This repository contains scripts and helpers for local cronjobs

• cronwrapper.sh - a wrapper script to call cronjob scripts
• inc_cronfunctions.sh - an include file that can be sourced in your bash scripts
• cronstatus.sh - ist shows status of all local cronjobs (and use cronwrapper.sh)
• cronlog-sync.sh - syncs logfiles to a central log server

To sync logfiles to a central log server there is script that detects new files in the logdir since the last sync.

#Requirements

Linux system with installed Bash. Tested on CentOS, Debian, Manjaro, Ubuntu.

I would say it runs on every system with GNU Bash. Non-GNU Bash was not tested.