On Sun, 30 Mar 2025 at 05:33, George Kirkham <[email protected]> wrote:
> 'Back in the good old days' when logging was to text files. When a disk > drive failed to boot, I could attach that disk drive to another computer > as a secondary drive, and then mount and read the logs to see why it > could no longer boot. As well as to inspect other things. [...] > Now with Journalctl, is it still possible to connect the failed-to-boot > disk drive to another computer and read logs? How? > Maybe the answer is to use -D or --directory to point to the attached > disk drives journal directory? [...] > Example: journalctl --directory=/path/to/your/journal/ > For example, journalctl --directory=/mnt/my_logs/journal > Is my interpretation of the man instructions correct? Hi, I did a simple test which confirms this works as you expect. 'journalctl --header' shows that the default directory is /var/log/journal, so my test command was: sudo journalctl --directory /otherdrive/var/log/journal
