• renzev@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 months ago

      I’m more of a runit guy, but I started using Alpine recently, and I have to say, openrc is also pretty nice!

      • msage@programming.dev
        link
        fedilink
        arrow-up
        0
        ·
        2 months ago

        What “scares” me the most is the journal… for some reason it takes too long to get specific unit logs, and should anything break down in it, there is no way for me to fix it. Like logging has been solved forever, and I prefer specific unit logs to the abomination of journalctl.

        But like unit files are everywhere, and systemctl at its core is a nice cmd utility.

        • Possibly linux@lemmy.zip
          link
          fedilink
          English
          arrow-up
          0
          ·
          2 months ago

          The thing with journalctl is that it is a database. Thus means that searching and finding things can be fast and easy in high complexity cases but it can also stall in cases with very high resource usage.

          • jj4211@lemmy.world
            link
            fedilink
            arrow-up
            0
            ·
            2 months ago

            Thing is that they could have preserved the textual nature and had some sort of external metadata to facilitate the ‘fanciness’. I have worked in other logging systems that did that, with the ability to consume the plaintext logs in an ‘old fashioned’ way but a utility being able to do all the nice filtering, search, and special event marking that journalctl provides without compromising the existence of the plain text.

            • Possibly linux@lemmy.zip
              link
              fedilink
              English
              arrow-up
              0
              ·
              2 months ago

              Plain text is slow and cumbersome for large amounts of logs. It would of had a decent performance penalty for little value add.

              If you like text you can pipe journalctl

              • jj4211@lemmy.world
                link
                fedilink
                arrow-up
                1
                ·
                2 months ago

                As I said, I’ve dealt with logging where the variable length text was kept as plain text, with external metadata/index as binary. You have best of both worlds here. Plus it’s easier to have very predictable entry alignment, as the messy variable data is kept outside the binary file, and the binary file can have more fixed record sizes. You may have some duplicate data (e.g. the text file has a text version of a timestamp duplicated with the metadata binary timestamp), but overall not too bad.