Hello Francesco P. Lovergine, Thanks for your feedback on this!
On Mon, Jul 03, 2023 at 06:17:20PM +0200, Francesco P. Lovergine wrote: > Uhm, it seems to me quite irritual using a template unit file without a > template variable. Which reflects > the quite strange use of /etc/default/vtun with multiple indexed vars, > instead of multiple configuration files such as: > > /etc/vtun.d/config?.vars (or even under /etc/vtun if you prefer so) > > and of course you can override the env variables by using an > /etc/vtun.d/%i.vars > > where it makes sense in the template file. I think this would be the right > moment to convert the > insane limited number of env var sets in /etc/default/vtun into multiple > ordinary configuration > files and using something like that. > > EnvironmentFile=-/etc/vtun.d/%i.vars > > would override name, host and args variables. > > I'm missing something? While I atleast partially agree with your initial sentence, I'm not onboard with your suggested solution. In my understanding use of EnvironmentFile= is discuraged (and if I'm not mistaken I've even read statements saying it was a mistake to ever add it as an option). It seems to me like you're bending over backwards trying to invent something that actually needs the instance variable. (I'm however fine with anything that gets things moving forward of using native units instead of init script. I'm also not even a user of this package/program as previously stated, so it affects me very little. Use what ever solution you find acceptable!) Regards, Andreas Henriksson
