I wrote an init script for autossh and thought it might be useful to include it with the ebuild. Note that this init script may do *too* much... we may want to cut down on the options it passes to ssh.
Created attachment 176276 [details] autossh This ebuild does require some directories to be installed on the machine, and an autossh user to be available. It needs the following directories /var/run/autossh (owned by autossh:daemon) /var/lib/autossh (owned by autossh:daemon) and an autossh user whose home dir is /var/lib/autossh
here is an example of the configuration file for it # global_alive_interval="15" # global_debug="yes" global_args_add="-c arcfour -2 -x" rtunnel_backup_host="user@host" rtunnel_backup_args="-R :10000:localhost:22" rtunnel_backup_master="no" # --------------- saikano_host="user@host" #saikano_debug="yes" socks5_host="user@host" #socks5_master="saikano" socks5_args="-D 10543" vnc_host="user@host" #vnc_master="saikano" vnc_args="-R 5900:172.16.15.14:5900 -R 5901:172.16.15.21:5901" #vnc_debug="yes" rtunnel_host="user@host" #rtunnel_master="saikano" rtunnel_args="-R :10000:localhost:22" The service_master is used instead of service_host when I want to use the ssh connection multiplexing. The host of the master will be used to connect
Created attachment 176277 [details] autossh Forgot to remove the local definition of a variable I didn't use anymore in start()
I don't think this is very useful at large unless you or someone else wants to maintain a more generic version of this. Closing as won't fix since it seems much too complex for my tastes.