If I’m using Arch or another minimal distro, is it a good idea to install a syslog daemon? Or can I go without?

    • LemmyHead@lemmy.ml
      link
      fedilink
      arrow-up
      2
      ·
      26 days ago

      I also don’t like the duplication of logs in journald and syslog, so I always disable forwarding to syslog

    • DeltaWingDragon@sh.itjust.worksOP
      link
      fedilink
      arrow-up
      0
      arrow-down
      2
      ·
      25 days ago

      What if I’m on another minimal distro, like Artix, that doesn’t use systemd? Journald is a systemd thing, and I’m not going to install systemd on top of a perfectly good init system.

      • nous@programming.dev
        link
        fedilink
        English
        arrow-up
        2
        ·
        25 days ago

        Use whatever that distro recommends then - which as far as I can tell seems to be svlogd for runit based systems. Though you should consult their documentation and make your own decision on which logger to use.

  • nerdovic@discuss.tchncs.de
    link
    fedilink
    Deutsch
    arrow-up
    2
    ·
    26 days ago

    Whatever floats your boat, but if something goes wrong you don’t really have anything to figure out what’s going on.

  • Mactan@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    26 days ago

    wish I knew how to use the journal, seems like there isn’t any good way to just search the previous session’s logs without a mountain of fuss or having to guess file names

    • MummifiedClient5000@feddit.dk
      link
      fedilink
      English
      arrow-up
      2
      ·
      26 days ago

      Check that you actually have persistent storage enabled. (See man journald.conf and search for Storage)

      Read up on the numerous parameters to journalctl. (man journalctl)

      journalctl --boot -2 will show logs from previous boot.

      journalctl --since "-2 weeks" --unit=sshd last two weeks worth of sshd logs.

  • bloodfart@lemmy.ml
    link
    fedilink
    arrow-up
    0
    ·
    26 days ago

    It’s often more useful for minimal installations to keep the system log daemon running so that you can see when things happen and stop them from happening.

    Especially now that even very low power embedded systems run multiple cpu cores at multi-ghz clocks, interface with gigabytes of memory, hundreds of gigabytes of attached storage and communicate through multi-gigabit network links, lots of stuff can be happening that is unwanted or simply unnecessary without any external indications.

    What are you trying to accomplish by not running a syslog daemon?

      • bloodfart@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        25 days ago

        If it’s a race from boot to login prompt then making sure the installer never has to dial out and retrieve packages would be a bigger savings. Making sure the installer is on the fastest bus possible would be huge too. I think one nvme installing to another one would be fastest (assuming enough lanes).

        Don’t take the wheelie bars off your dragster to save weight, wheelies are slow.