This sounds like an issue for your system. In general, the FHS is a
guide for software developers; when you set things up to write or read
data of various types, here's where you should place them. If this is
your system, you're free to do what you want.
One option would be to permanently mount a persistent filesystem in
/var/log/journal, but given that this is a Raspberry Pi, you may not
have that flexibility.
So, I'd create something like /local for local data of this nature, and
bind mount under that, to something like /local/journal. But that's
just a suggestion.
If I've misunderstood, let me know, and I'll see if I can be more helpful.
On 1/26/20 3:38 PM, Dave wrote:
It's quite common on the Raspberry Pi to make /var/log a tmpfs, in
order to reduce the number of writes to the SD card that is the pi's
main storage. That's quite acceptable for most logs but I'd like to
make journald's logs persistent so I'll be able to investigate any
crashes more easily.
It's not possible to tell journald to log somewhere other than
/var/log/journal, so I need to bind mount another directory on a
persistent filesystem over /var/log/journal
The question is, where should that other directory be placed in the
filesystem? /var/lib/journal sounds attractive except FHS 3.0 says "...
should not be logging output ...". So where should persistent log files
be kept, if /var/log is a tmpfs?
TIA, Dave
_______________________________________________
fhs-discuss mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/fhs-discuss
_______________________________________________
fhs-discuss mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/fhs-discuss
