• remotelove@lemmy.ca
    link
    fedilink
    arrow-up
    52
    arrow-down
    2
    ·
    edit-2
    1 year ago

    Binary logs are annoying, but once you get the hang of journalctl, it’s not so bad. That is about my only remaining hate for it.

    In its early days, it was a serious pain. Its service management was annoying and is still a bit scattered to this day. It has improved a ton, for sure.

    Then there was PID 1. Here is a legacy discussion about it as I refuse to talk any more about it these days: https://news.ycombinator.com/item?id=10485131

    Above all else, it was kinda forced on us. Most of us were comfortable with sysv already. If I remember correctly, people often said the main dev for systemd could be a real jackass. I have no judgement or experience regarding that though.

    • IsoKiero@sopuli.xyz
      link
      fedilink
      English
      arrow-up
      18
      arrow-down
      2
      ·
      1 year ago

      Above all else, it was kinda forced on us. Most of us were comfortable with sysv already.

      And at least for me it solved a problem which didn’t exist. Sure, there’s some advantages, but when it rolled out it was a huge pain in the rear and caused various problems and made things more complicated for no apparent reason.

    • kill_dash_nine@lemm.ee
      link
      fedilink
      English
      arrow-up
      10
      ·
      1 year ago

      Yeah, I can easily remember the commands to tail the logs because it’s journalctl -fu and I always think “fuck you” as I’m typing that.

    • kbotc@lemmy.world
      link
      fedilink
      English
      arrow-up
      4
      ·
      1 year ago

      Most of the bolted on services are rather shitty. ResolveD in particular is straight up hot garbage unless the only thing you are comparing it to is nscd. I like shipping all my logs to a centralized service and journald just gets in the way. It feels like they took upstart, bolted on some really crappy daemons,