https://github.com/axelhahn/cronwrapper
bash scripts to improve handling of cronjobs
https://github.com/axelhahn/cronwrapper
bash cronjob crontab monitoring shell
Last synced: about 2 months ago
JSON representation
bash scripts to improve handling of cronjobs
- Host: GitHub
- URL: https://github.com/axelhahn/cronwrapper
- Owner: axelhahn
- Created: 2019-01-23T22:29:02.000Z (over 7 years ago)
- Default Branch: master
- Last Pushed: 2026-01-15T09:05:22.000Z (5 months ago)
- Last Synced: 2026-05-01T12:53:00.192Z (about 2 months ago)
- Topics: bash, cronjob, crontab, monitoring, shell
- Language: Shell
- Homepage:
- Size: 1.27 MB
- Stars: 5
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: readme.md
Awesome Lists containing this project
README
Axels
```text
|
A X E L S --x--
______ ________ |
| |.----.-----.-----. | | | |.----.---.-.-----.-----.-----.----.
| ---|| _| _ | | | | | || _| _ | _ | _ | -__| _|
|______||__| |_____|__|__| |________||__| |___._| __| __|_____|__|
|__| |__|
```
Unix shell scripts in Bash for easier handling of cronjobs.\
A little idea that offers more possibilities.
Free software and Open source.
👤 Author: Axel Hahn \
📄 Source: \
📜 License: GNU GPL 3.0 \
📗 Docs: see [www.axel-hahn.de/docs](https://www.axel-hahn.de/docs/cronwrapper/)
## 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.
