Re: [systemd-devel] logging in RAM and journald configuration issue

2019-04-02 Thread Lennart Poettering
On Di, 02.04.19 17:42, Dave Howorth (syst...@howorth.org.uk) wrote: > On 2019-03-20 Lennart Poettering wrote: > > > On Mi, 20.03.19 18:08, Dave Howorth (syst...@howorth.org.uk) wrote: > > > > > > > > At present AFAICT the log2ram.service runs > > > Before=systemd-journald.service and various

Re: [systemd-devel] logging in RAM and journald configuration issue

2019-04-02 Thread Dave Howorth
On 2019-03-20 Lennart Poettering wrote: > On Mi, 20.03.19 18:08, Dave Howorth (syst...@howorth.org.uk) wrote: > > > > > At present AFAICT the log2ram.service runs > > Before=systemd-journald.service and various other services, so I > > think that aspect is covered. > > I am not sure what this

Re: [systemd-devel] logging in RAM and journald configuration issue

2019-03-21 Thread Umut Tezduyar Lindskog
Back then, this is something we have tried and it works. Not with bind mount though. We also have SD-card as primary storage. As soon as the storage service mounted the SD-Card, we have created a symbolink link under /var/log to the persistent and triggered journald flush. It worked just fine! On

Re: [systemd-devel] logging in RAM and journald configuration issue

2019-03-20 Thread Dave Howorth
This message was caught up in what looks like a freedesktop server crash so I'm reposting it slightly edited after other responses. Hopefully it will now reach the list and thread somewhat sensibly. > Lennart Poettering wrote on 20/03/2019 13:37: > > On Mi, 20.03.19 09:57, Dave Howorth

Re: [systemd-devel] logging in RAM and journald configuration issue

2019-03-20 Thread Lennart Poettering
On Mi, 20.03.19 18:08, Dave Howorth (syst...@howorth.org.uk) wrote: > > At present AFAICT the log2ram.service runs > Before=systemd-journald.service and various other services, so I think > that aspect is covered. I'd be careful with that. If you have a service that runs before journald you need

Re: [systemd-devel] logging in RAM and journald configuration issue

2019-03-20 Thread Colin Guthrie
Lennart Poettering wrote on 20/03/2019 13:37: > On Mi, 20.03.19 09:57, Dave Howorth (syst...@howorth.org.uk) wrote: > >>> On Di, 19.03.19 20:45, Dave Howorth (syst...@howorth.org.uk) wrote: >>> In the case of a machine that uses an SD card as its primary backing store, it is desirable

Re: [systemd-devel] logging in RAM and journald configuration issue

2019-03-20 Thread Lennart Poettering
On Mi, 20.03.19 09:57, Dave Howorth (syst...@howorth.org.uk) wrote: > > On Di, 19.03.19 20:45, Dave Howorth (syst...@howorth.org.uk) wrote: > > > > > In the case of a machine that uses an SD card as its primary backing > > > store, it is desirable to reduce the number of write operations to > > >

Re: [systemd-devel] logging in RAM and journald configuration issue

2019-03-20 Thread Dave Howorth
> On Di, 19.03.19 20:45, Dave Howorth (syst...@howorth.org.uk) wrote: > > > In the case of a machine that uses an SD card as its primary backing > > store, it is desirable to reduce the number of write operations to > > the card in order to prolong its life. journald is quite > > well-behaved in

Re: [systemd-devel] logging in RAM and journald configuration issue

2019-03-20 Thread Lennart Poettering
On Di, 19.03.19 20:45, Dave Howorth (syst...@howorth.org.uk) wrote: > In the case of a machine that uses an SD card as its primary backing > store, it is desirable to reduce the number of write operations to the > card in order to prolong its life. journald is quite well-behaved in > this regard

[systemd-devel] logging in RAM and journald configuration issue

2019-03-19 Thread Dave Howorth
In the case of a machine that uses an SD card as its primary backing store, it is desirable to reduce the number of write operations to the card in order to prolong its life. journald is quite well-behaved in this regard since it offers the choice of a temporary or permanent journal and limits the