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 _at_....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
--x+6KMIRAuhnl3hBn
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBAgAGBQJTzuLoAAoJENvmPC7PRKkIyQoQAKaRBoUKoqUYGmVSZspiy5AD
6Bvhd/gn44HQLgGL53K/ssuaVaUk5uT3o2OvorQjYh+fL9WkGdcnPNWe2pnIAbVJ
Fd5BTWKRpjvvmLWmIBKKYgNR2tqO4lXDrAa97nI6W84IEimpFUc/vDcmAbkRVxa8
RG5YzMtnYrKAXbmbyAJm7C3s0ySC4rPh9H2Be8UBPU5glJGQ9aJcHQqDl0RKYxXf
/botYYLL0sfQXoLaVrA3WVWTyhZ1mRl1E8zWR48U8V+GsEIzr8hIrn1dW88X5kGY
nrpQPdkhtLvYBSE8/8PdGZwgw9EGNiOT0z1LGOiPCXVYfWp38Pkx7P3xNqJYvZ49
KclIRqXD/7DArJz/Wp5p8Iv4byMoTDItXYrI7F5/NMK7z6yBgTzWYNmXdgynTz3U
PoandFaoAVcleZ9iQXvPf/bFDi48FaQ6gZTcBscCvIt8Ze6ECu3cicuX1HU32nOb
T2TuKGlRyzDROPR1JG03xVcjyTiP1fvQ3F3m9BxOyM83ZzLDap4gRrZEzbdjEnHh
iMGi1DHaF33Wf5TElhSetTgOmY/mnbqTbfGJyukhvoHQde3ZbGNDLD0N5nYLKjzG
/PbvKLPe+DZyhWgH4WXo8vFarIAVwyIY7T11HC96bW99L1ZjGbKbNwrJUpTSdIDp
hLzoiA29Pv3BIVTQqFEy
=VZKW
-----END PGP SIGNATURE-----
--x+6KMIRAuhnl3hBn--
Received on Tue Jul 22 2014 - 22:17:12 UTC
This archive was generated by hypermail 2.3.0
: Sun May 09 2021 - 19:44:18 UTC