[Date Prev]   [Date Next] [Thread Prev]   [Thread Next] [Date Index]   [Thread Index]


     Re: [nocol-users] hostmon telnet problem

On Tue, 2 Mar 1999, Lee Huynh wrote:

> Date: Tue, 02 Mar 1999 19:50:17 -0500
> From: Lee Huynh <lhuynh@MCI.NET>
> To: nocol-users@navya.com
> Cc: lhuynh@MCI.NET
> Subject: [nocol-users] hostmon telnet problem
> Hello nocol experts,
>   [Can I not use "telnet" and use ssh/scp instead for hostmon? deleted]
> Lee.
> Senior Network and System Administrator
> MCIWorldCom.

This should be in the archive (IS there an "archive" of the list?), but,
I think it's sort of "unfair" to call it a "telnet" client... it's really
simply a clear-tect socket to the hostmon port (5455 by default?) to the
client machine -- "telnet" is just an easy way to explain it, if you ask
me.  That is, the server goes through its list of client and tries to
connect to each of them on the port that you've defined for hostmon...
if the connection is successful, and if the client has the "nlog host"
defined as the host from which that connection was establshed, the
client simply dumps its current monitorlist variables back to the server
on that socket.  If the connection fails, the server then defers rsh/rcp
for that host... which, of course, is easily replaced by ssh/scp.

Unfortunately, I've heavily modified hostmon (maybe someday my changes
will be posted back to the list or given to Vikas -- once they're
actually somewhat useful).  You can look in the hostmon code... look for
the string "Try telnetting to the hostmon port" (about line 475, I think?)
to see the initial attempt at the socket... about 41 lines beyond that
is the rcp (about line 516?) that you will probably want to change (or
just kill the rsh/rcp binaries and link them to you ssh/scp binaries --
they should be nearly drop-in replacements, after all... at least, that
is their intention).

Hope that helps...


Russell M. Van Tassell