Re: netdev templates and location of network units

["Kevin P. Fleming" <kevin@xxxxxxx>]

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 /usr/local/lib/systemd/network though, so if they aren't
being picked up that's odd.

https://www.freedesktop.org/software/systemd/man/systemd.network.html

On Mon, Mar 23, 2020 at 6:51 AM Christian Schneider
<cschneider@xxxxxxxxxxxxx> wrote:
>
> 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 custom service files are, though.
> Since this was a bit surprising, I want to ask, what is the rationale
> behind this, and what would be the recommended location of the
> network/netdev files? Right now we placed them in /etc/systemd/network
>
> Furthermore, since we make heavy use of vlan, I tried to create a
> template netdev file where the instance goes in as vlan id, but when I
> tried to reference instance of the template in the network file, I got
> syntax errors. Is there a rational behind this or is it just not
> implemented to be use templates for netdev?
>
> BR, Christian
>
> _______________________________________________
> systemd-devel mailing list
> systemd-devel@xxxxxxxxxxxxxxxxxxxxx
> https://lists.freedesktop.org/mailman/listinfo/systemd-devel
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel