Filippo Giunchedi wrote:
...how to know if the server will correctly reply to alive messages
sent by the client? This also requires knowing what protocol version
is being used.
True. As I recall, that feature requires version 2.0 of the protocol. I
forgot about that.
Of course the ssh client knows this, and could be designed to use
randomly selected monitoring ports as a fallback (and without the race
condition that the wrapper script has). But that requires patching OpenSSH.
My point is that with aliveinterval enabled it becomes rather easy to
implement something like autossh with a shell script...
The autossh author said likewise.
With most of the heavy lifting having already been implemented in
OpenSSH, it might be a good time to develop a patch for OpenSSH to
finish the job, if anyone is so inclined.
This would provide additional advantages over autossh as well, such as
having logic to distinguish between temporary network failures and
permanent syntax, startup, or protocol failures.
...anyhow it can be considered as an option to the debian wrapper.
Right, I could see it still being useful as a matter of convenience, as
long as the limitations are documented and it can be disabled. Maybe if
-M 0 disables the monitoring, -M -1 could cause the wrapper to trigger
the OpenSSH built-in monitoring? (The script would pass -M 0 on to autossh.)
-Tom
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
