Return to Answer

noticed that someone else had already given the inittab and Upstart configurations

Source Link

edited Jun 6, 2015 at 23:52

ExitOnForwardFailure yes is a good adjunct to the other suggestions. If it connects but can't establish the port forwarding it's just as useless to you as if it hadn't connected at all.

and yet another way to restart, on non-Upstart systems, is to use a line in /etc/inittab, something like:

tunl:2345:respawn:/usr/bin/ssh -n -N -T -R 0:6789:localhost:22 me@myserver

Upstart of course can be configured similarly but it's a bit more complicated.

ExitOnForwardFailure yes is a good adjunct to the other suggestions. If it connects but can't establish the port forwarding it's just as useless to you as if it hadn't connected at all.

and yet another way to restart, on non-Upstart systems, is to use a line in /etc/inittab, something like:

tunl:2345:respawn:/usr/bin/ssh -n -N -T -R 0:6789:localhost:22 me@myserver

Upstart of course can be configured similarly but it's a bit more complicated.

ExitOnForwardFailure yes is a good adjunct to the other suggestions. If it connects but can't establish the port forwarding it's just as useless to you as if it hadn't connected at all.

Source Link

created Jun 6, 2015 at 23:41

jcomeau_ictx

ExitOnForwardFailure yes is a good adjunct to the other suggestions. If it connects but can't establish the port forwarding it's just as useless to you as if it hadn't connected at all.

and yet another way to restart, on non-Upstart systems, is to use a line in /etc/inittab, something like:

tunl:2345:respawn:/usr/bin/ssh -n -N -T -R 0:6789:localhost:22 me@myserver

Upstart of course can be configured similarly but it's a bit more complicated.