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?
The idea would be to make the motitoring engine some kind of always
running daemon. When needed, the display portion of tkined could be
fired up from any X location.
I'd like to be able to have the monitoring functionality of tkined left
running on a server without having to have X fired up and a user logged
in. What do you think?
I've played a bit with the currently existing remote functionality. When
a remote tkined connects to another, what really happens? How does the
client interact with the server? Does the client simply display what
the server is doing, or does it run a completely independent session
using a map downloaded from the server?
I've got many more questions, but I'll give it a rest for now... :-)
thanks,
--- ------------------------------------------------------------------------- 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 -------------------------------------------------------------------------