On Fri, Sep 25, 2015 at 09:31:09AM +0300, Răzvan Sandu wrote: > From the point of view of a Red Hat *user*, the standardised way of doing > things would be to have > an /etc/sysconfig/tinc file containing something like: > > NETWORKS="vpn1 vpn2 vpn3" (one or more names separated by spaces) > > At initialization, each name should launch a separate tinc instance (a > different VPN)
Unfortunately, this is not something that maps well to systemd. It would require a systemd to run a script that parses the sysconfig file and start all the tinc daemons. Systemd will then put all those daemons in the same control group and won't recognize something is wrong if only one of the daemons fail. So backwards compatibility with the old way Red Hat did it is not really the way to go. > As for the tinc.service file itself, a good start would be, IMHO: > > https://leesjohn.wordpress.com/2013/03/13/how-to-automatically-start-tinc-on-fedora-17/ That one has the drawback that it only starts one tinc daemon, and you have to edit the service file to specify the netname. -- Met vriendelijke groet / with kind regards, Guus Sliepen <[email protected]>
signature.asc
Description: Digital signature
_______________________________________________ tinc mailing list [email protected] http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
