On Sun, Mar 12, 2017 at 10:43:07PM +0100, Sebastian Schmachtel wrote:
> sorry i was not aware, that /etc/nets.boot is no longer working for
> autostarting a network. Had I read News.Debian.gz in the doc folder, I
> would have known ;-).
No problem. Maybe I should have it modify /etc/tinc/nets.boo
Hey,
sorry i was not aware, that /etc/nets.boot is no longer working for
autostarting a network. Had I read News.Debian.gz in the doc folder, I
would have known ;-).
On Sun, Mar 12, 2017 at 10:22:46PM +0100, Sebastian Schmachtel wrote:
> after boot:
>
> root@oimel:/home/prisma# systemctl status tinc
> ● tinc.service - Tinc VPN
>Loaded: loaded (/lib/systemd/system/tinc.service; enabled; vendor
[...]
> root@oimel:/home/prisma# systemctl status tinc@malteser
Hi,
after boot:
root@oimel:/home/prisma# systemctl status tinc
● tinc.service - Tinc VPN
Loaded: loaded (/lib/systemd/system/tinc.service; enabled; vendor
preset: enabled)
Active: active (exited) since Sun 2017-03-12 13:39:25 CET; 8h ago
Main PID: 1275 (code=exited, status=0/SUCCESS)
T
On Mon, Oct 17, 2016 at 04:38:34AM -0400, clayton wrote:
> However
>
> systemctl start tinc@netname.service
>
> DOES work. And thereafter
>
> systemctl restart tinc.service &
> systemctl stop tinc.service
>
> work correctly. I can reproduce this at least on two recent stretc
Package: tinc
Version: 1.0.29-1
Severity: normal
However
systemctl start tinc@netname.service
DOES work. And thereafter
systemctl restart tinc.service &
systemctl stop tinc.service
work correctly. I can reproduce this at least on two recent stretch installs.
-- System
6 matches
Mail list logo