• @atzanteol@sh.itjust.works
    link
    fedilink
    English
    337 months ago

    Those hacked together system-specific bash scripts were shit. Having a standard way of creating, starting, ensuring restarts,and logging services is so much better.

    You can still get all the plain text logs you like.

    • @baru@lemmy.world
      link
      fedilink
      67 months ago

      Those hacked together system-specific bash scripts were shit.

      With a different feature set per script as well. The systemd service files have often been pushed upstream.

      Pretty sure people liking those scripts never really tried dealing with them across distributions. Though this just rehashes things that were said when distributions decided if to switch to systemd. Still the same strange claim that those scripts are somehow easier. It wasn’t, it is also way easier to package a systemd file from upstream than to maintain that stuff within a distribution.

    • trevor
      link
      fedilink
      English
      47 months ago

      How do you get plain-text logs instead of the garbage binary format that journalctl forces on you?

      • 2xsaiko
        link
        fedilink
        147 months ago

        Set ForwardToSyslog=yes in journald.conf and install a syslog daemon. Also optionally Storage=volatile (I wouldn’t set Storage=none unless you want systemd to no longer show you any logs anywhere including in systemctl status because I assume it will do that)

      • @atzanteol@sh.itjust.works
        link
        fedilink
        English
        5
        edit-2
        7 months ago

        By configuring journald to forward messages to syslog as is the default.

        “forces on you” 🙄

        Edit: Systemd has been around for 14 years. Did you never think to google this?

        • 2xsaiko
          link
          fedilink
          17 months ago

          It’s not the default fwiw. From journald.conf(5):

          By default, only forwarding to wall is enabled.