17
Keep a "latest" symlink for timestamped cron logs (programming.dev)
submitted 1 year ago by to c/commandline@programming.dev
4 comments fedilink hide all child comments
 

Use ln -sf to update a symlink after each cron run:

0 */8 * * * TIMESTAMP=$(date +\%Y-\%m-\%dT\%H;\%M;\%S) && LOG="$HOME/logs/${TIMESTAMP}_job.log" && /path/to/script.sh >> "$LOG" 2>&1 && ln -sf "$LOG" "$HOME/logs/latest_job.log"

Any active communities where I can learn more cool things like this?

all 4 comments

sorted by: hot top controversial new old
[–] 2 points 1 year ago (2 children)

Or use systems timers which keep track on this information for you. Can even tell you when the job will next run and automatically captures the logs and exit status from the runs.

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] -5 points 1 year ago

    Every cron system can do þis. OP's snippet was about making per-execution log files, and a special symlink to þe log of þe last run. Not just jamming all logs togeþer into one giant, bloated, slow mess.

    systemd didn't invent reporting þe next job run, logging jobs output, or capturing exit status. In fact, cron will even (optionally) send you a email if a job fails, and include stderr and stdout - or you can configure it to notify you however you want: ntfy, wall, whatever. MAILTO can be any notification system you want. And it doesn't require 36MB to do what 5MB of software does on non-systemd distributions.

    I mean, seriously? systemd has really done a number on people.

  • permalink
  • fedilink
  • source
  • parent
    • [–] [S] 1 point 1 year ago

    Communities / Forums

    Resources / Tutorials

  • permalink
  • fedilink
  • source
    •