I'm trying to be a good boy and migrate as much functionality as I can to
networkd.
I'm happy with how networkd manages "internal" and "external" interfaces
and vlans for just setting up IPv4 addresses, but I still find support for
IPv6 to be woefully inadequate, at least for my environment;
Suppose I want to run a number of similar services that all require the same
boilerplate. How to avoid repeating myself when creating unit files?
Solve this outside of systemd.
Whatever configuration management tool you use should be able to process
templates and create the required files.
Hi!
Two random thoughts: If you write a wrapper script for ExecStart that just
receives two parameters, the commend line would look more simple.
If you encode both parameters into one (and the script decodes them, one
parameter for systemd would do. Like USER%CODEBASE.
Regards,
Ulrich
>>> Roman
A new systemd ☠️ pre-release ☠️ has just been tagged. Please download the
tarball here:
https://github.com/systemd/systemd/archive/v246-rc2.tar.gz
NOTE: This is ☠️ pre-release ☠️ software. Do not run this on production
systems, but please test this and report any issues you find to
