One drawback to switching the CVS_RSH environment variable to `fsh' is that only half of my CVS repository servers have in.fshd available (or provide me with enough access to install it and/or Python). Might it be possible for `fsh' to have a fallback mode, whereby if in.fshd cannot be executed on the remote system, that `fsh' will just transparently exec ssh?
Ben
Ben Elliston bje@redhat.com writes:
One drawback to switching the CVS_RSH environment variable to `fsh' is that only half of my CVS repository servers have in.fshd available (or provide me with enough access to install it and/or Python). Might it be possible for `fsh' to have a fallback mode, whereby if in.fshd cannot be executed on the remote system, that `fsh' will just transparently exec ssh?
This is certainly needed. It is probably the most important thing to do with fsh no. Some ideas are present in the Bugzilla bugtracking system. See http://bugzilla.lysator.liu.se/show_bug.cgi?id=315
Some of the ideas there are probably too complex. It would be better to have something that works now, than a very fancy solution two years from now. I'll see what I can do. (Code contributions are always welcome.)
/ceder