Am Mittwoch, 1. August 2012 schrieb Michael Biebl: > On 31.07.2012 21:05, Martin Steigerwald wrote: > > technical arguments like its Linux only and I found some limitations > > myself like its init script compabitibility does not take care of > > further initscript arguments like for openvpn initscript to tell it > > which VPN to start due to not supporting something like this at its > > design level > > As Tollef told you in [1], systemd solves this kind of issue with > instanced services. This is not a "limitation" at its "design level", > it just means that sysvinit and systemd solve this particular problem > in a different way which can't be mapped via a compat layer.
Use case is: /etc/init.d/openvpn start myvpn or some other vpn, as I wish. I understood Tollef´s comment as that I need several service files for several VPNs. In that understanding I saw a limitation at the design level. But I see now in „man systemd.service“ that it is possible to use environment variables in the ExecStart option, thus it should be possible to do something like this – I thought this would only be possible for variables systemd provides by itself: VPN=myvpn systemctl start openvpn.service which would be similar enough. > [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682615#10 Thanks, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201208011907.51551.mar...@lichtvoll.de