ssh -vvv doesn't tell me where the failure happens. For now I have
given up on ssh and am just working on RSH. Seems that nobody knows
how to set RSH up on clusters. Problem is that 500+ ssh sessions can
eat p CPU time on the master in a hurry. Problem is that RSH has no
debugging information at all.. Closest I have gotten is getting
xinetd to warn on startup errors. Whats a guy got to do to get
information from his daemons? =)
(BTW, Why does everybody shrug off rsh? For clusters its perfectly
acceptable and if the cluster is large enough then its nearly required.)
On Nov 13, 2005, at 2:30 PM, Donnie Berkholz wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Brady Catherman wrote:
| And whats up with the SSH/RSH developers not giving some form of
| debugging method? I mean.. The only thing you get for logging is
login
| notices. I can't find any way to get useful debugging out of RSH.
Does `ssh -vvv` not give any useful debugging info?
| Whats most frustrating is that this is effortless on Fedora. Very
| little file modification is needed.
It might be interesting to look at any patches they apply that they've
failed to send upstream.
Thanks,
Donnie
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDd757XVaO67S1rtsRAkQ0AJ0f99ZqR8Vj+kivbbe6GlkOBGWh4QCeKM8X
s6g8i99oiMOZwGe1DONA+pM=
=aFX4
-----END PGP SIGNATURE-----
--
[email protected] mailing list
--
[email protected] mailing list
