Răzvan Sandu
2015-Sep-25 10:25 UTC
tinc initialization (in both Red Hat and Debian families)
La 25.09.2015 13:00, tinc-request at tinc-vpn.org a scris:> 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.Hello, IMHO, it's *unavoidable* that the systemd initialization reads some sort of configuration file and learns from it how many tincd processes it should launch and which VPN name for each. If the configuration file tinc.conf remains VPN-dependent ( *different* tinc.conf files for VPN1, VPN2, etc., located under /etc/tinc/VPN1, /etc/tinc/VPN2, etc.) the above-mentioned configuration file cannot be tinc.conf So I thought one may use /etc/sysconfig/tinc instead. Of course, this has the disadvantage of being Red Hat-specific; it would be *great* to have, for that role, a configuration file that resides in a common place, for both Red Hat and Debian families. Best regards, R?zvan -------------- partea urm?toare -------------- Un ata?ament HTML a fost eliminat URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20150925/e5acc85f/attachment.html>
Guus Sliepen
2015-Sep-25 11:31 UTC
tinc initialization (in both Red Hat and Debian families)
On Fri, Sep 25, 2015 at 01:25:19PM +0300, R?zvan Sandu wrote:> IMHO, it's *unavoidable* that the systemd initialization reads some sort of > configuration file and learns from it how many tincd processes it should > launch and which VPN name for each.It is totally avoidable by using templates. As I mentioned before, using the systemd service files that I added to git here: http://tinc-vpn.org/git/browse?p=tinc;a=tree;f=systemd;hb=refs/heads/1.1 With those two, you can enable and start any number of tinc instances, like this: systemctl enable tinc at foo systemctl enable tinc at bar systemctl start tinc This will instantiate two units for tinc with netnames foo and bar respectively, and the last line will start both of them. -- Met vriendelijke groet / with kind regards, Guus Sliepen <guus at tinc-vpn.org> -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20150925/3a4349b3/attachment.sig>
Apparently Analagous Threads
- tinc initialization (in both Red Hat and Debian families)
- tinc initialization (in both Red Hat and Debian families)
- Tinc + OSPF - is it feasible?
- How to set Subnet in a node which act as both server and client role?
- How to set Subnet in a node which act as both server and client role?