Re: [systemd-devel] Tempering the Logging Data when Knowing the Verification Key / Time Synchronization

2021-10-11 Thread Lennart Poettering
On Mo, 11.10.21 17:08, Andreas Krueger (andreas.krue...@fmc-ag.com) wrote: > Hi Folks, > > > I am currently working in an embedded project that uses Journal for logging. > The logging data shall be protected by the Journal's sealing mechanism FSS > and for various reasons the verification key

[systemd-devel] Tempering the Logging Data when Knowing the Verification Key / Time Synchronization

2021-10-11 Thread Andreas Krueger
Hi Folks, I am currently working in an embedded project that uses Journal for logging. The logging data shall be protected by the Journal's sealing mechanism FSS and for various reasons the verification key is located unprotected in memory. Regarding this constellation, my first question is

Re: [systemd-devel] dm-integrity volume with TPM key?

2021-10-11 Thread Lennart Poettering
On Fr, 08.10.21 21:15, Sebastian Wiesner (sebast...@swsnr.de) wrote: > Am Montag, dem 04.10.2021 um 14:49 +0200 schrieb Lennart Poettering: > > On Do, 30.09.21 21:20, Sebastian Wiesner (sebast...@swsnr.de) wrote: > > > > > Hello, > > > > > > thanks for quick reply, I guess this explains the lack

Re: [systemd-devel] [systemd]: How to set systemd not to generate loop0.device and mtdblockx.device?

2021-10-11 Thread Lennart Poettering
On Sa, 09.10.21 11:27, www (ouyangxua...@163.com) wrote: > systemd version: V242 > > In our system, the whole machine starts too slowly. We want to do > some optimization. I found that two services( loop0.device and > mtdblock5.device) started slowly. I want to remove them (I > personally think

Re: [systemd-devel] [systemd]: How to set systemd not to generate loop0.device and mtdblockx.device?

2021-10-11 Thread Colin Guthrie
Hi, www wrote on 09/10/2021 04:27: In our system, the whole machine starts too slowly. We want to do some optimization. I found that two services( *loop0.device and mtdblock5.device*) started slowly. I want to remove them (I personally think our system are not need them). I want to ask you

Re: [systemd-devel] Antw: [EXT] Re: [systemd‑devel] Q: write error, watchdog, journald core dump, ordering of entries

2021-10-11 Thread Lennart Poettering
On Mo, 11.10.21 10:57, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de) wrote: > > Now when journald hangs due to some underlying IO issue, then it might > > miss the watchdog deadline, and PID 1 might then kill it to get it > > back up. It will log about this to the journal, but given tha tthe >

[systemd-devel] Antw: [EXT] Re: [systemd‑devel] Q: write error, watchdog, journald core dump, ordering of entries

2021-10-11 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 11.10.2021 um 09:54 in Nachricht : > On Mi, 06.10.21 10:29, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de) wrote: > >> Hi! >> >> We had a stuck networkc card on a server that seems to have caused the RAID > controller with two SSDs to be stuck on write as

Re: [systemd-devel] Q: write error, watchdog, journald core dump, ordering of entries

2021-10-11 Thread Lennart Poettering
On Mi, 06.10.21 10:29, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de) wrote: > Hi! > > We had a stuck networkc card on a server that seems to have caused the RAID > controller with two SSDs to be stuck on write as well. > Anyway journald dumped core with this stack: > Oct 05 20:13:25 h19