Day 10 - Getting the computer to do your work for you

https://linuxupskillchallenge.org/10/

16 points · 6 comments · view on lemmy.world

6 Comments

sin_free_for_00_days@sopuli.xyz · 4 pts · 2y (2 replies)

I always wonder why at isn't mentioned more in these types of articles.

SpaceNoodle@lemmy.world · 3 pts · 2y (1 reply)

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.

sin_free_for_00_days@sopuli.xyz · 2 pts · 2y

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.

fnmain@programming.dev · 3 pts · 2y

I think, rough estimation, my server which is running Arch would last ~1 month with auto updating on

bhamlin@lemmy.world · 3 pts · 2y

I honestly wouldn't recommend this for any server, and probably not for a workstation. This is useful for learning but could easily be a nightmare when troubleshooting an issue on a remote machine.

It's always a great idea to do updates when you can give them your attention. Even if it's you triggering them via ansible or other automation.

livialima@programming.dev · 1 pts · 2y