Hi!
I just made an "interesting" observation: When running "journalctl -f" there is
no message when journald restarts, meaning you'll have to restart "journalctl
-f", too to see any messages after journald has been restarted.
Is this the way it is designed?
(systemd-234-24.64 of SLES15 SP2)
So this is the eventual rule I ended up writing after having a lot of
trouble writing a udev rule:
`ACTION=="add", SUBSYSTEM=="ata_port", KERNEL=="ata[0-9]",
TEST=="../../power/control" ATTR{../../power/control}="auto"`
Here is the rule working:
```
Dec 01 01:33:16 arch systemd-udevd[267]:
Hi!
I forgot: What I'd expect at least to see in the "old" journalctl -f is this
log message:
-- Logs begin at Wed 2020-11-25 11:27:53 CET. --
Nov 30 12:03:27 h19 systemd-journald[957]: Received SIGTERM from PID 1
(systemd).
Regards,
Ulrich
>>> "Ulrich Windl" schrieb am 30.11.2020
um
12:08 in
On Mon, Nov 30, 2020, 23:25 Zheng, Fam wrote:
> Hi,
>
> Currently in systemd-networkd.service we have
>
> After=... systemd-udevd.service ...
>
> I know the point of it has been for tuntap as pointed out by comments
> above, but I do wonder what ensures the ordering of NIC drivers (as
> loaded
