60
Are you using systemd or an alternative, what do you recommend? (lemmy.ml)
submitted 6 months ago by to c/linux@lemmy.ml
68 comments fedilink hide all child comments
 

What are some significant differences to expect when switching to an alternative, and can that affect gaming compatibility and performance?

you are viewing a single comment's thread
view the rest of the comments
[–] 28 points 6 months ago (9 children)

The main functional difference between systemd and others is that systemd will just work. Others will require you hand tune and hand tinker with a non-mainstream Linux distro.

If your hobby is init systems by all means mess around though.

I personally quite like systemd. Unit files are clean, timers services and sockets are easy to manage etc.

Honestly it’s a non-problem. Best advice is to use what is best supported. Don’t let the extremely fringe (but loud) tiny group of systemd haters throw you off.

  • permalink
  • fedilink
  • source
  • hideshow 9 child comments
    •
  • [–] 10 points 6 months ago (8 children)

    As someone who's created a timer, cron is much more straightforward.

    Systemd has its good points, but most of that is the core functionality as a sysvinit replacement in my opinion. And it's entirely likely that at least one of the newer alternatives is a better option for that.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 8 child comments
    •
  • [–] 21 points 6 months ago* (last edited 6 months ago) (6 children)

    I think if you know cron from the start it can be easier, but it gets really annoying really fast.

    Compare:

    0 0 * * * /usr/bin/flock -n /tmp/myjob.lock bash -c 'sleep $((RANDOM % 3600)) && /usr/local/bin/myjob.sh'

    To:

    [Timer]
OnCalendar=daily
RandomizedDelaySec=1h

    That and things like systemd preventing overlapped delays, handing what to do if the system was down during the last cycle, built in logging and event tracking. Seeing successful vs non successful runs etc.

    Once you add in those production requirements cron gets annoying fast and timers are easy.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 4 points 6 months ago (4 children)

    For adding a quick thing to make something happen at a specific time, I can add a cron job in a couple of minutes. To add a timer takes creating a couple of files with syntax that took me a while to look up last time I needed it, and running a command. Then debugging. Sure, the timer has benefits, but cron jobs are still simpler.

    On the bright side, there's actually a "crontab -t" command that apparently can be used to generate timer files from a crontab line, which I hadn't known of before today.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 14 points 6 months ago (2 children)

    That’s because you know cron. If you knew timers equally as well they would be easier. And they let you handle the edge cases (retry, randomness, tracking, logs etc) without the need for a custom script.

    Once you factor in the production edge cases I think timers are clearly easier. You get all of it for free.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 6 months ago (1 child)

    As someone who didn't know anything about either a short time ago, I found cron easier to learn and use. Systemd timers look more visually clean, but the way cron works is more simple and straightforward.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 5 points 6 months ago*

    I can see how for some people cron is more straightforward to learn, at least till you need to handle logging, checking for cron results, handling when the triggered event can’t happen that instance, ensuring only one instance of the triggered thing happens at once, adding time jitter, etc.

    Then timers are way simpler. Timers let you create robust timed events for free. With cron you need to do all that yourself.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 11 points 6 months ago

    I can add the two files required to run a timer in systemd in a couple minutes, but writing the complex incantation to cron for having it do something that is the default in systemd is pure pain and takes me 3 hours of googling

  • permalink
  • fedilink
  • source
  • parent
  • [–] -1 points 6 months ago

    Something looks more complicated is not a problem. Compare long division to a calculator, why would one think the calculator is more elegant? The calculator only enabled those who can't do math acquire the answer.

    And somehow in modern time, learning is someone who should be ashamed of??? Since when?

  • permalink
  • fedilink
  • source
  • parent