- cross-posted to:
- linuxupskillchallenge@programming.dev
- linuxupskillchallenge@programming.dev
- linuxupskillchallenge@programming.dev
- linuxupskillchallenge@programming.dev
- linuxupskillchallenge@programming.dev
- linuxupskillchallenge@programming.dev
- linuxupskillchallenge@programming.dev
- linuxupskillchallenge@programming.dev
- linuxupskillchallenge@programming.dev
- cross-posted to:
- linuxupskillchallenge@programming.dev
- linuxupskillchallenge@programming.dev
- linuxupskillchallenge@programming.dev
- linuxupskillchallenge@programming.dev
- linuxupskillchallenge@programming.dev
- linuxupskillchallenge@programming.dev
- linuxupskillchallenge@programming.dev
- linuxupskillchallenge@programming.dev
- linuxupskillchallenge@programming.dev
I always wonder why
atisn’t mentioned more in these types of articles.probably because at appears to just be for scheduling single tasks, not recurring ones - but thanks for mentioning it, since I wasn’t aware of it before.
Ah, my bad. I saw the systemd timers thing, and not knowing much about systemd I figured that was an alternative closer to at than cron. Looks like it’s more of another unneeded replacement. I use at all the time and only really edit my cron a few times a year. I’d think that I’d learn to read entire articles before commenting.