Each time the system boot the boot gets a boot id, that way if you want to look something up from a specific boot you can just use the boot id or the or the pointer to view the logs from a specific boot. For example you run the following.
Code:
journalctl --list-boots | head -6
IDX BOOT ID FIRST ENTRY LAST ENTRY
-26 27c5b1e726074052a6f00d2569d23710 Tue 2023-11-14 07:23:01 CET Tue 2023-11-14 21:48:46 CET
-25 00bf5be744ee4c68a0921573ae71d218 Wed 2023-11-15 07:28:34 CET Wed 2023-11-15 23:57:45 CET
-24 ea291177a21a400bbe716192424b8840 Thu 2023-11-16 07:45:13 CET Thu 2023-11-16 21:36:45 CET
-23 ec856be145b645baa2bd0bc4698edc8b Fri 2023-11-17 08:43:21 CET Sat 2023-11-18 01:33:18 CET
-22 787fd27f6b9e4078ae01326cf9ef5e4c Sat 2023-11-18 09:15:12 CET Sat 2023-11-18 23:01:23 CET
You can then just use the pointer which points to view that boot journal.
Or you can use the boot id to view all the logs of that boot.
Code:
journalctl -b 27c5b1e726074052a6f00d2569d23710
Some of the most compelling advantages of systemd are those involved with process and system logging. Using other systems, logs are usually dispersed through…
www.digitalocean.com