30.11.2015, 15:47, "Konstantin Tokarev" <annu...@yandex.ru>: > 30.11.2015, 15:39, "Matt Johnston" <m...@ucc.asn.au>: >>> On Mon 30/11/2015, at 7:24 pm, Konstantin Tokarev <annu...@yandex.ru> >>> wrote: >>> dbclient: Remote TCP forward request failed (port 3320 -> localhost:22) >>> >>> ... >>> 1. Is there any way to force dbclient to exit in this case? >>> 2. If not, would it be reasonable feature to have in dbclient? >> >> Hi Konstantin, >> >> I can't think of a good way to force exit apart from grepping the command >> output for the error message. >> >> I'd like to see that as a feature - I was thinking about it a few days ago. >> I'd keep it under a command line flag for backwards compatibility. Failing >> to bind "-L" forward ports would also be handled similarly. >> >> I'll put it on the todo list, or patches accepted. > > Could you propose command line option name? I guess the main problem is to > avoid collision with OpenSSH client options.
Maybe its time to add -o and use OpenSSH-compatible -o ExitOnForwardFailure=yes? -- Regards, Konstantin
