Ok, thx for the input. Since I have v239 on the embedded device, that's
the explanation.
BR, Christian
Am 23.03.20 um 14:40 schrieb Andrei Borzenkov:
> 23.03.2020 14:15, Kevin P. Fleming пишет:
>> Input files for systemd-networkd are not systemd unit files, so
>> there's a good chance that the
23.03.2020 14:15, Kevin P. Fleming пишет:
> Input files for systemd-networkd are not systemd unit files, so
> there's a good chance that the rules for finding and processing them
> are much simpler. That would explain why template/instance files don't
> work.
>
> The manpage for systemd.network
Input files for systemd-networkd are not systemd unit files, so
there's a good chance that the rules for finding and processing them
are much simpler. That would explain why template/instance files don't
work.
The manpage for systemd.network does indicate that files will be
loaded from
Hi all,
for an embedded device with Linux and systemd boot, we wanted to deploy
custom network and netdev units.
We tried placing them in /usr/local/lib/systemd/network, next to service
files for custom services in /usr/local/lib/systemd/system. The network
units aren't picked up by systemd, the
I don't understand your answer/information at all. I wanted to know
how to use unprivileged port with systemd-timesyncd - and I got
information that it has sane defaults. So how should I read your
answer? Is there something in systemd that still makes it insecure?
Should I add some other parameter