Logbookd: Difference between revisions
WhyNotHugo (talk | contribs) (Initial write-up: short intro, setup instructions, short hint on old logs.) |
WhyNotHugo (talk | contribs) (Add Category:Services) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 9: | Line 9: | ||
Setting it up is quite straightforward: | Setting it up is quite straightforward: | ||
apk add logbookd | |||
# Disable and stop the default syslog. | |||
rc-update del syslog boot | |||
service syslog stop | |||
# Enable and start logbookd | |||
rc-update add logbookd boot | |||
service logbookd start | |||
After the next reboot, you may want to review previous log files in <code>/var/log</code>, which will remain unused and stale. Only the sqlite database should remain relevant. | |||
= See also = | |||
* [https://blog.brixit.nl/looking-closer-at-the-syslog/ Looking closer at the syslog]: an introductory article to syslog and logbookd. | |||
[[Category:Services]] | |||
Latest revision as of 09:10, 7 July 2024
logbookd is a syslogd implementation that uses an sqlite database as a backend.
The default mode of operation uses a reduced write mode, where lots are written to memory and only flushed to disk when the service is interrupted or receives SIGUSR1.
Setup
Logbook is provided via the logbookd package.
Setting it up is quite straightforward:
apk add logbookd # Disable and stop the default syslog. rc-update del syslog boot service syslog stop # Enable and start logbookd rc-update add logbookd boot service logbookd start
After the next reboot, you may want to review previous log files in /var/log, which will remain unused and stale. Only the sqlite database should remain relevant.
See also
- Looking closer at the syslog: an introductory article to syslog and logbookd.