Hello,

I have a few processes logged by svlogd, as shown below.

pstree output

runit─┬─chronyd
      ├─dhcpcd
      ├─mdadm
      .
      .
      ├─runsvdir─┬─5*[runsv───agetty]
      │          ├─runsv─┬─atd
      │          │       └─svlogd
      │          ├─runsv─┬─crond
      │          │       └─svlogd
      │          ├─runsv─┬─login───xinit─┬─X───{X}
      │          │       │               └─xmonad-x86_64-l─┬─remind
      │          │       │                                 ├─7*[st───tmux]
      │          │       │                                 ├─xautolock
      │          │       │                                 ├─xmobar
      │          │       │                                 └─xmobar───ledmon
      │          │       └─svlogd
      │          ├─runsv─┬─acpid
      │          │       └─svlogd
      │          ├─runsv─┬─klogd
      │          │       └─svlogd
      │          └─runsv─┬─svlogd
      │                  └─syslogd


I find svlogd log files hard to read as the lines have a UTC timestamp(-tt)
and the filenames with @....s are hard to understand. I read that
svlog files are meant to be processed by a post-processor.

I use logrotate for other log files.

Just wanted to check if anyone could please share some insight on how
they manage/post-process svlogd generated logs.

In the runit documentation, I saw multilog and svlogd both being
used. When do you use multilog over svlogd?

Thanks
Joe

Attachment: signature.asc
Description: Digital signature

Reply via email to