I’ve been having the same issue with Ubuntu, thankfully we have access to Upstart:
``` start on (local-filesystems and net-device-up IFACE!=lo) stop on stopping network-services author "Mark Lopez" description "Tinc Upstart Job" version "0.1" env network=master respawn exec /usr/sbin/tincd -n "$network" -D --debug=3 --logfile ``` I removed the default init script and switched over to Upstart. Restarts will occur as soon as the process dies. Save the job as “/etc/init/tinc.conf”. From: tinc [mailto:[email protected]] On Behalf Of Daniel J. Grinkevich Sent: Friday, January 29, 2016 8:25 AM To: [email protected] Subject: Re: respawning dead tinc process This is what we use on our routers, running once a minute via crontab. if pgrep "tincd" >/dev/null; then echo "tincd is running" else echo "tincd isn't running, restarting" tincd -n nycmesh fi On Fri, Jan 29, 2016 at 9:07 AM, pjv <[email protected]<mailto:[email protected]>> wrote: I have tinc 1.1pre11 running on various routers and linux cloud servers. On one of the cloud servers, under Ubuntu 12.04, tinc is mysteriously dying once in a while, leaving a dangling PID. I have been unable to track down why it is dying, but it happens infrequently enough that I care less about why it is dying than how to robustly respawn it when it dies. Before I re-invent the wheel, has anyone come up with a solution for automatically detecting a dead tincd and respawning the process on linux? _______________________________________________ tinc mailing list [email protected]<mailto:[email protected]> http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc -- --- GPG Key: 0x160B24D1C08FB4E4<https://pgp.mit.edu/pks/lookup?op=get&search=0x160B24D1C08FB4E4>
_______________________________________________ tinc mailing list [email protected] http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
