• Damage@feddit.it
    link
    fedilink
    arrow-up
    48
    ·
    edit-2
    4 days ago

    Ok so I’m just my own system administrator, yet I like systemd because I remember how much less… reliable the former alternatives were on my computers.

    BUT. I dislike having to learn more commands just to read my logs, and systemd timers are awfully complicated when I just needed what cronjobs already did.

    • Laser@feddit.org
      link
      fedilink
      arrow-up
      8
      ·
      edit-2
      4 days ago

      You can use systemd with the classic logging tools by installing and enabling their respective service if you prefer. This will forward all messages to them. You even get a more comprehensive log than before systemd as the latter will even forward the messages that were sent before the logging service was started.

      Edit: similarly for cron, you can still use the classic tools. I see their appeal in ease of configuration. Though in my opinion, systemd timers are more powerful and better integrated (don’t ask me why, I made that assessment years ago) so I accept that increased complexity.

      For logs, I actually prefer the systemd journal though

    • Amon@lemmy.worldOP
      link
      fedilink
      arrow-up
      4
      ·
      4 days ago

      Yeah but you can use journalctl on literally everything from binaries to units to cron jobs with the same interface. You don’t need to find the log file just punch it into journalctl