M
mike_cole
I am hoping someone here can help me find a way around this problem.
Here is my setup: I have a Perl script residing on a Win2003 machine.
The Perl script will start a console app and some time later will send
a ctrl-c to the console app in order to close it down in an orderly
fashion. It accomplishes this by finding the window with the title of
the app, bringing that window to the foreground and sending the ctrl-c.
This works fine when I kickoff the script from that machine, but when I
telnet into the machine and kick off the script via telnet, it no
longer works. I believe this is because when I launch the app via
Telnet, a process is started but a window is not created for that
process. I don't want to kill the process since this may leave things
in a messy state afterwards. Sending a ctrl-c allows the console app to
cleanup before it closes. Does anybody know a way around this?
Mike
Here is my setup: I have a Perl script residing on a Win2003 machine.
The Perl script will start a console app and some time later will send
a ctrl-c to the console app in order to close it down in an orderly
fashion. It accomplishes this by finding the window with the title of
the app, bringing that window to the foreground and sending the ctrl-c.
This works fine when I kickoff the script from that machine, but when I
telnet into the machine and kick off the script via telnet, it no
longer works. I believe this is because when I launch the app via
Telnet, a process is started but a window is not created for that
process. I don't want to kill the process since this may leave things
in a messy state afterwards. Sending a ctrl-c allows the console app to
cleanup before it closes. Does anybody know a way around this?
Mike