[systemd-devel] openvpn at .service

[Michael D. Berger]

> -----Original Message-----
> From: 
> systemd-devel-bounces+m.d.berger=ieee.org at lists.freedesktop.or
> g 
> [mailto:systemd-devel-bounces+m.d.berger=ieee.org at lists.freede
sktop.org] On Behalf Of Michal Schmidt
> Sent: Wednesday, November 16, 2011 06:39
> To: systemd-devel at lists.freedesktop.org
> Subject: Re: [systemd-devel] openvpn at .service
> 
> On 11/15/2011 10:10 PM, Mirco Tischler wrote:
> > 2011/11/15 Manuel Amador (Rudd-O)<rudd-o at rudd-o.com>:
> >> It's a multi-instance service.  You can instance it several times 
> >> based on a parameter, much like tty at .service can be 
> instantiated to 
> >> be tty at tty1.service.
> 
> Correct. In the instances of openvpn at .service the @ should be 
> followed by the name of the config file that the instance 
> will use (without the .conf suffix).
> 
> > Most certainly it is a socket activated service in the inetd style, 
> > i.e. one service instance per connection.
> 
> inetd-style socket activated services use template units too, 
> but openvpn at .service in F16 is not an inetd-style service.
> 
> Michal

[...]

On my old system, after setting up keys and well documented
scripts and config files, I started openvpn with:

   /etc/init.d/openvpn start

. On F16_64 can I now do:

   systemctl start openvpn.service

, or perhaps:

   systemctl start openvpn at .service

, or do I have to do something else?

Thanks,
Mike.

--
Michael D. Berger
m.d.berger at ieee.org
http://www.rosemike.net/