Dave Abrahams <[email protected]> writes: Hi Dave,
>>> And... if contacting the host repeatedly failed it might be good for >>> Tramp to get out of the way and stop intervening for the next few >>> seconds. I've just committed a patch to Tramp's repository. If a connection has been failed, the next 5 seconds connection attempts to that host won't be accepted. This is not configurable (yet), but we could change it. OTOH, there are too many defcustom's already in Tramp ... >> That's an idea. But what shall Tramp do then to "get out of the way"? >> Returning an error? It does, and it annoys. Returning nil? > > I don't know enough about Tramp internals to guess what function is > "returning" in your questions above, nor in what context it's being > called. I meant, essentially, turning itself off for any server that > fails. If Tramp is asked to establish the same connection N times in M > seconds, and it fails, that connection could be (temporarily?) put on a > "do not try" list... and then for paths specifying that connnection > Tramp might simply act as though it doesn't exist. That's what it does for now. I haven't seen another obvious solution. > Thinking about this some more, that might be too simplistic. I guess I > was sort of counting on you to take the general idea and make it > workable. Let's see how it works in practice. At least Tramp is tracing everything what it does :-) Whether this is understandable for the user - I hope. Saying this, I won't synchronise this patch with Emacs' trunk. This might be too offending for software in feature freeze. Best regards, Michael. _______________________________________________ Tramp-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/tramp-devel
