logread(1)
π logread(1) β your bestie's guide to the logbookd log fetcher β¨
okay so welcome to the logread page!! this is from the General Commands Manual and honestly it's giving tiny-but-mighty π
β¨ NAME β¨
logread β fetch log messages from the logbookd socket π«Ά
πΈ SYNOPSIS πΈ
logread [OPTIONS]
OPTIONS := { -f | -F | -n limit | -d datefmt | -u unit | -b boot | -c
color | -h }
like, you just run logread with some options and it goes and gets your logs, no big deal π
(the synopsis literally spells out the whole options set for you, so slay)
π¦ DESCRIPTION π¦
so basically: logread connects to the running logbookd instance and queries the database for old or realtime log messages. that's it. that's the whole vibe. you want logs, it has logs, everyone's happy πβ¨
π OPTIONS π
-hβ show the help message and quit. the classic "please tell me what's going on" button π-c { on | off }β force enable or disable the colorized output. yes queen, control the aesthetic yourself π π-fβ show only new log messages as they come in, in realtime. main character energy: you only care about what's happening right now β-Fβ show log messages as they come in, but first output the historical log messages. so you get the backstory and the live feed, obsessed π«Ά-n countβ number of historical log messages to fetch after filtering. defaults to100. and bestie, listen: if you pass0, the amount of messages is not limited π (that's a lot of logs, you've been warned)-d datefmtβ override the datetime formatting in the log output. defaults to%b %d %H:%M:%S. make it pretty, make it yours π-u unitβ show only log messages for this specific service. this matches the prefix of the syslog"app"field. filtering by app? iconic πΈ-b { boot-index | boot-id | "list" }β get only the log messages matching a specific boot-id. this parameter accepts the boot as a relative index or as an uuid to specify an absolute boot event. and use the special value"list"to display a list of stored boot logs instead πβ¨
ngl the -b one is lowkey the most powerful one here β relative index or uuid, your choice, iykyk π
π SEE ALSO π
logbookd(1)β the other half of this whole situation, go read it fr fr π¦
and that's the page!! π this was logread from the General Commands Manual, version/date situation being logread Β· 2026-03-06 Β· logread(1) β mwah, go fetch those logs bestie, periodt ππ
π¦ where this page comes from
- alpine 3.24: logbookd-doc 0.2.4-r3 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms