Hi,
I have a question about the bus benchmark. On the v238, the benchmark only
works with the input chart direct. If I put another input, the program gets
an assertion failure. Also, what chart, bisec, legacy, direct means?
There's no documentation come with the benchmark. I wonder what that outpu
Hi,
Yeah, unfortunately that log line is very misleading (and has actually
been removed in more recent versions of systemd for this reason!)
Ultimately this is something which you should debug via your distro
support channels as disk encryption is ultimately implemented quite
differently in vario
Ugh, looks like that message had gotten lost in spam somehow... Sorry for all the noise!
--
Ryan (ライアン)
Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone else
https://refi64.com/On Colin Guthrie , Mar 27, 2018 4:11 AM wrote:Perhaps you missed Lennart's reply?
I have to say it
Hi
I am not quite sure to post at the right place. I do so because I got
the following lines when running "journalctl -xb" in a Ubuntu xenial
system, and more precisely
"Support:http://lists.freedesktop.org/mailman/listinfo/systemd-devel";.
I added lines on # to border output from command lines
Dimitri John Ledkov wrote on 26/03/18 11:34:
> Hello,
>
> When systemd-networkd-wait-online was originally introduced, it was
> the only tool that correctly waited and blocked the boot, until after
> networking is configured.
>
> These days, however, all/most network configurations tools ship
> a
Perhaps you missed Lennart's reply?
I have to say it doesn't sound like the right place to fix things.
Really the daemon needs to be fixed.
What you suggest sounds quite racy generally (at least the
WantsFileBefore= bit anyway) and really is just to paper over a badly
written daemon that also bre
