Re:separating the monitoring engine from the display
George Eddy (eddy@ISI.EDU)
Thu, 18 Jan 96 14:03:57 PST
According to: > I'm relatively new to this list, so please forgive if this has been
> discussed before...
>
> Has any consideration been given to the idea of splitting tkined up so
> that the network monitoring engine can run without the X display portion?
> [...]
> ---
> -------------------------------------------------------------------------
> Charles Owens Email: owensc@enc.edu
> "I read somewhere to learn is to
> Information Technology Services remember... and I've learned that
> Eastern Nazarene College we've all forgot..." - King's X
> -------------------------------------------------------------------------
>
I think scotty is what you are looking for. scotty has all the
"network monitoring" functionality and is purely character based.
tkined has no network monitoring capabilities built in, it simply
starts a script (usually scotty, but not necessarily) and
communicates with it via stdio. the script is actually doing the
network monitoring and tells tkined to update the display via "ined
..." commands.
tkined remote facility uses simple rpc mechanism provided by scotty.
take a look at the ~scotty-x.x.x/tkined directory to get a feel for
how this works, it's rather elegant, i might add! and i think
accomplishes what your looking for.
--
- rusty
eddy@isi.edu