| 1 |
ssh -vvv doesn't tell me where the failure happens. For now I have |
| 2 |
given up on ssh and am just working on RSH. Seems that nobody knows |
| 3 |
how to set RSH up on clusters. Problem is that 500+ ssh sessions can |
| 4 |
eat p CPU time on the master in a hurry. Problem is that RSH has no |
| 5 |
debugging information at all.. Closest I have gotten is getting |
| 6 |
xinetd to warn on startup errors. Whats a guy got to do to get |
| 7 |
information from his daemons? =) |
| 8 |
|
| 9 |
(BTW, Why does everybody shrug off rsh? For clusters its perfectly |
| 10 |
acceptable and if the cluster is large enough then its nearly required.) |
| 11 |
|
| 12 |
|
| 13 |
On Nov 13, 2005, at 2:30 PM, Donnie Berkholz wrote: |
| 14 |
|
| 15 |
> -----BEGIN PGP SIGNED MESSAGE----- |
| 16 |
> Hash: SHA1 |
| 17 |
> |
| 18 |
> Brady Catherman wrote: |
| 19 |
> | And whats up with the SSH/RSH developers not giving some form of |
| 20 |
> | debugging method? I mean.. The only thing you get for logging is |
| 21 |
> login |
| 22 |
> | notices. I can't find any way to get useful debugging out of RSH. |
| 23 |
> |
| 24 |
> Does `ssh -vvv` not give any useful debugging info? |
| 25 |
> |
| 26 |
> | Whats most frustrating is that this is effortless on Fedora. Very |
| 27 |
> | little file modification is needed. |
| 28 |
> |
| 29 |
> It might be interesting to look at any patches they apply that they've |
| 30 |
> failed to send upstream. |
| 31 |
> |
| 32 |
> Thanks, |
| 33 |
> Donnie |
| 34 |
> -----BEGIN PGP SIGNATURE----- |
| 35 |
> Version: GnuPG v1.4.2 (GNU/Linux) |
| 36 |
> |
| 37 |
> iD8DBQFDd757XVaO67S1rtsRAkQ0AJ0f99ZqR8Vj+kivbbe6GlkOBGWh4QCeKM8X |
| 38 |
> s6g8i99oiMOZwGe1DONA+pM= |
| 39 |
> =aFX4 |
| 40 |
> -----END PGP SIGNATURE----- |
| 41 |
> -- |
| 42 |
> gentoo-cluster@g.o mailing list |
| 43 |
> |
| 44 |
|
| 45 |
-- |
| 46 |
gentoo-cluster@g.o mailing list |
Archives