🚀 go-pugleaf

> dan@ortta.umn.edu (Daniel C. Cummings) writes:
>Has anyone using LWP 4.1 with the XPC program noticed that the server PC (
>the host with XPC loaded) must be at a DOS prompt for XPC to respond to an 
>incoming Telnet session?  Is there a way around this?  It would be nice to 
>be able to telnet to your office PC, start up a process (say a program 
>compile, or a large database sort), break the connection (Control-x, q) and 
>then be able to telnet in later to check on it's progress *while the program 
>is still running on the host PC*.  Or as another example, have an endless 
>loop batch file running on the host PC to always force the incoming telnet 
>session to a particular application.  But alas, when this is done, the 
>host PC acts like it's busy and won't respond.....
>
>Part of what I'm after could also be achieved if it was possible to tell 
>XPC to do some command upon a successful connection (like run a batch file) 
>or upon a broken connection (say...reboot the PC).....any Novellers out 
>there with any suggestions??

The third party product, Everywhere Access allows you to retelnet in,
or reboot on closure, or prevent future logins, and it has a user API
in case you want to execute things upon openning or closing sessions.
It works with LWP.

Contact info@snsi.com for details.


-- 
----------------------------------------------------------------------------
Erick Engelke				 	            WATTCP Architect
erick@development.uwaterloo.ca     TCP/IP was easy but i still can't work VI