Livia Lima@programming.devM to Linux Upskill Challenge@programming.dev · 6 months ago

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

linuxupskillchallenge.org

6
17

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

linuxupskillchallenge.org

Livia Lima@programming.devM to Linux Upskill Challenge@programming.dev · 6 months ago
6
Day 10 - Getting the computer to do your work for you - Linux Upskill Challenge
linuxupskillchallenge.org
A month-long course aimed at those who aspire to get Linux-related jobs in the industry - junior Linux sysadmin, DevOps-related work, and similar. Learn the skills required to sysadmin a remote Linux server from the commandline.
    • SpaceNoodle@lemmy.world
      3·
      6 months ago

      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·
        6 months ago

        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·
    6 months ago

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

  • Billegh@lemmy.world
    3·
    6 months ago

    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.