RE: killing a process by window title; was: socket application
Vidyadhar,
I didn't respond earlier as I was pretty busy at work and this is a rather
detailed request. In addition this is, in my mind, not really Perl related.
That said, I'm stuck home under a few feet of snow tonight and can spend
some time on this for you.
The basic problem is that the two processes are owned by different
primaries. In order to do what you want to do, my first thought is to
impersonate the user's credentials. The big problem there is that you
probably don't have the user's password. My next thought is that since you
seem to be targeting a specific application, it may be easier to look at the
process list, rather than the windows on the desktop. Let's take a stab at
this approach... (opening Komodo)...
--8<--CODE-->8--
#!perl.exe
use strict;
use warnings;
# Included Modules
use Win32::Process;
use Win32::ToolHelp;
# Locate window by executable name
my $pID= 0;
my $iFlags = 0;
my $pname = "notepad.exe";
my( @Process ) = Win32::ToolHelp::SearchProcess($pname);
unless( Win32::Process::Open( $pID, $Process[1], $iFlags )) {
print "Win32::Process::Open => ".
Win32::FormatMessage(Win32::GetLastError())."\n";
}
# Kill identified process
my $uExitCode = 0;
$pID->Kill( $uExitCode );
__END__
--8<--CODE-->8--
I compiled the above with PerlApp and then scheduled it with an AT command.
It killed the copy of notepad.exe running in my user process. It does seem
that $pname is case sensitive so be careful when recompiling this for your
target application. Hope that this helps you out...
Chris
> -Original Message-
> From: Jangale V-S [mailto:[EMAIL PROTECTED]]
> Sent: Monday, February 17, 2003 11:09 PM
> To: [EMAIL PROTECTED];
> [EMAIL PROTECTED]
> Subject: FW: killing a process by window title; was: socket
> application
>
>
> Somebody help please !!
>
> -Original Message-
> From: Jangale V-S
> Sent: 13 February 2003 11:06
> To: [EMAIL PROTECTED];
> [EMAIL PROTECTED]
> Subject: RE: killing a process by window title; was: socket
> application
>
>
> Further to this topic I have a slightly different requirement.
>
> I want to kill process running on interactive desktop (with
> interactive
> user's login) through scheduler .
>
> The background is
>
> User logged on interactively on a machine are running one application
> which they sometimes leave ON overnight .
>
> A process is running thr schduler (using different user
> account which is
> administrator account) which has to update certain files
> related to above
> application. For this the applcation has to be terminated/closed after
> verifying
> window title !
>
> Now how can I get/enumerate windows which are open in
> interactive user's
> desktop ?
>
>
> With Best Regards,
>
> Vidyadhar
>
> ___
> Perl-Win32-Admin mailing list
> [EMAIL PROTECTED]
> To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
> ___
> Perl-Win32-Admin mailing list
> [EMAIL PROTECTED]
> To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
>
LEGAL NOTICE
Unless expressly stated otherwise, this message is confidential and may be privileged.
It is intended for the addressee(s) only. Access to this E-mail by anyone else is
unauthorized. If you are not an addressee, any disclosure or copying of the contents
of this E-mail or any action taken (or not taken) in reliance on it is unauthorized
and may be unlawful. If you are not an addressee, please inform the sender immediately.
___
Perl-Win32-Users mailing list
[EMAIL PROTECTED]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
FW: killing a process by window title; was: socket application
Somebody help please !! -Original Message- From: Jangale V-S Sent: 13 February 2003 11:06 To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: killing a process by window title; was: socket application Further to this topic I have a slightly different requirement. I want to kill process running on interactive desktop (with interactive user's login) through scheduler . The background is User logged on interactively on a machine are running one application which they sometimes leave ON overnight . A process is running thr schduler (using different user account which is administrator account) which has to update certain files related to above application. For this the applcation has to be terminated/closed after verifying window title ! Now how can I get/enumerate windows which are open in interactive user's desktop ? With Best Regards, Vidyadhar ___ Perl-Win32-Admin mailing list [EMAIL PROTECTED] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs ___ Perl-Win32-Users mailing list [EMAIL PROTECTED] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
RE: killing a process by window title; was: socket application
Dirk, Rob, et. al.,
OK... I couldn't leave it alone. I sat down and cleaned up the code. I
have replace the API calls with calls to Win32::Process and Win32::GUI, and
have improved the error handling. I also reformatted the lines to try to
prevent my mailer from wrapping them wrong. They look a little weird, but
they should execute fine. This latest cut at the application is below.
Remember to watch your task bar... Notepad is only alive for two seconds.
Now it's time to get back to the code I'm getting paid for! ;)
Chris
--8<--CODE-->8--
#!perl.exe
use strict;
use warnings;
# Included Modules
use Win32::Process;
use Win32::GUI;
# Spawn new process
my $pID;
my $App = "$ENV{windir}\\notepad.exe"; # Application
my $Cmd = "$App c:\\temp\\test.txt";# Full command line
my $fResult = Win32::Spawn( $App, $Cmd, $pID );
# Forget the process ID
$pID = 0;
# Stuff happens
sleep(2);
# Locate window by name or class
my $lpClassName = "Notepad";
my $lpWindowName = "";
my $iFlags= 0;
my $hWnd = Win32::GUI::FindWindow( $lpClassName, $lpWindowName );
print "FindWindow => ".
Win32::FormatMessage(Win32::GetLastError())."\n"
if( $hWnd == 0 );
my( $pTID, $lpdwProcessId ) = Win32::GUI::GetWindowThreadProcessId($hWnd);
print "GetWindowThreadProcessId => $lpdwProcessId\t$pTID\t".
Win32::FormatMessage(Win32::GetLastError())."\n"
if( $lpdwProcessId == 0 );
unless( Win32::Process::Open( $pID, $lpdwProcessId, $iFlags )) {
print "Win32::Process::Open => ".
Win32::FormatMessage(Win32::GetLastError())."\n";
}
# Kill identified process
my $uExitCode = 0;
$pID->Kill( $uExitCode );
__END__
--8<--CODE-->8--
LEGAL NOTICE
Unless expressly stated otherwise, this message is confidential and may be privileged.
It is intended for the addressee(s) only. Access to this E-mail by anyone else is
unauthorized. If you are not an addressee, any disclosure or copying of the contents
of this E-mail or any action taken (or not taken) in reliance on it is unauthorized
and may be unlawful. If you are not an addressee, please inform the sender immediately.
___
Perl-Win32-Users mailing list
[EMAIL PROTECTED]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
RE: killing a process by window title; was: socket application
> -Original Message- > From: Sisyphus [mailto:[EMAIL PROTECTED]] > - Original Message - > From: "Dirk Bremer (NISC)" <[EMAIL PROTECTED]> > > > > Some of the lines of your script were wrapped bu email, so > I hope that I > > reconstructed them correctly. I found I first needed to install the > > Win32::API and Win32::API::Prototype modules, which I did. > When running > your > > script, I recieved the following error messages on Win2K. > Note that the > > instance on Notepad was never spawned. > > > > 2492306 The specified procedure could not be found. > > > > 1692484 The specified procedure could not be found. > > > > 100 The specified procedure could not be found. > > > > I'm sure that something is wrong at my end, any thoughts on > this will be > > appreciated. > > > > Dirk, > I'm getting the same (the numbers change each time I run it) - but the > instance of notepad *is* being spawned and then killed 2 > seconds later. > However, the notepad instance is being spawned in a minimised > state - so > unless I'm actually looking at the task bar when I run the script, the > creation and subsequent destruction goes by unnoticed. > I imagine the same is happening for you. > > Cheers, > Rob > Based upon the output, Rob's diagnosis is probably correct. I didn't really do any serious error checking... the output was more for my own information and I forgot to strip it out of the code. Since it's being displayed, let me explain what it means: Line 1: The number is the window handle of the window with the specified title. The error message is the last reported Win32 error, REGARDLESS of whether an error actually occured. Line 2: The first number is the process id for the window handle. This is the number that we shows up in the task manager and that we REALLY need to kill the process. The second number is the thread id for the window handle and is just a side-effect of obtaining the process id. Once again, the error message is the last reported Win32 error. Since it didn't change, we must not have had an error. Line 3: The number is the handle that we just opened with "terminate permissions" that we will use to kill the process. Please note that I forgot to close this handle so there is a small memory leak in this code! (Apparently, I didn't do any QC on this stuff!) One again, the error message is the last reported Win32 error. If you want a cleaned up copy of the code, I can tweak it up and e-mail it to you. Since you'll have to rework it a little to do what you REALLY wanted to do, I'd rather just leave it as a proof-of-concept and let you take it from here. I have since learned that it's probably possible to replace the Kernel32.dll calls with Win32::Process::Open and Win32::Process::Kill, but don't have a working example yet. Christopher J. Gerber * Senior Systems Analyst, PGM IT Systems Unit * Eastern Point Rd, Bldg 90, Rm 324, MS 9090, Groton, CT 06340-9090 * Work: +1.860.441.5876 -- FAX: +1.860.715.7041 * Pager: +1.860.743.1698 -- Alpha: +1.800.772.4387 PIN# 0651367 LEGAL NOTICE Unless expressly stated otherwise, this message is confidential and may be privileged. It is intended for the addressee(s) only. Access to this E-mail by anyone else is unauthorized. If you are not an addressee, any disclosure or copying of the contents of this E-mail or any action taken (or not taken) in reliance on it is unauthorized and may be unlawful. If you are not an addressee, please inform the sender immediately. ___ Perl-Win32-Users mailing list [EMAIL PROTECTED] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Re: killing a process by window title; was: socket application
> Now, getting the window title I don't know about. I was about to suggest
> Win32::Console::Title, but that, I believe, is only the command window
(if
> any) that is running the current script.
>
> Anyone?
>
I would try using Win32::API with autoitdll.dll (hiddensoft.com). I tested
the snippet below and it does the trick. (There is a more forcefull call of
WinKill if the app is not responding).
use Win32::API;
# void WINAPI AUTOIT_SetTitleMatchMode(
# int nMode
# );
my $autoit_match_mode = new Win32::API("AutoItDLL",
"AUTOIT_SetTitleMatchMode", [I], V);
# void WINAPI AUTOIT_WinClose(
#char *szTitle,
#char *szText
# );
my $autoit_close = new Win32::API("AutoItDLL", "AUTOIT_WinClose", [P,P],
V);
$autoit_match_mode->Call(1);
$autoit_close->Call("test.txt - Notepad", ""); # leaves other instances of
Notepad alone
Steve
___
Perl-Win32-Users mailing list
[EMAIL PROTECTED]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
killing a process by window title; was: socket application
This seems like a useful starting point, courtesy of Dave Roth: http://www.roth.net/perl/scripts/scripts.asp?ProcList.pl In Python, I sometimes use one of the distribution scripts called killProcName.py. Here's an excerpt which can probably be translated to Perl without too much difficulty: handle = win32api.OpenProcess(win32con.PROCESS_TERMINATE, 0,pids[0]) win32api.TerminateProcess(handle,0) win32api.CloseHandle(handle) I believe that it should be possible to synthesize these two pieces of information and produce a solution. Jonathan At 03:34 PM 1/28/2003 -0600, Dirk Bremer (NISC) wrote: >- Original Message - >From: "Gerber, Christopher J" <[EMAIL PROTECTED]> >To: "'Dirk Bremer (NISC)'" <[EMAIL PROTECTED]> >Sent: Tuesday, January 28, 2003 15:25 >Subject: RE: socket application > > >> Dirk, >> >> I had hacked together something like this in C at one point. I think I >have >> a copy of the source code at home. I'll see if I can find it and then we >> can talk about turning it into Perl. If I can't find it, I should at >least >> be able to find the API calls. Are the processes that you're killing >> regular apps, or services. (Services would be easier.) >> >> Chris >> > >Chris, > >They are not services and written in the WinBatch scripting language that >supports the creation of its own windows. They are not console windows per >se, but similar. I have used something in Win32::GUI to locate a particular >window by its title, but have no idea how to kill the window once it has >been located. > >Dirk Bremer - Systems Programmer II - ESS/AMS - NISC St. Peters >USA Central Time Zone >636-922-9158 ext. 8652 fax 636-447-4471 > >[EMAIL PROTECTED] >www.nisc.cc > >___ >Perl-Win32-Users mailing list >[EMAIL PROTECTED] >To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs ___ Perl-Win32-Users mailing list [EMAIL PROTECTED] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Re: socket application
- Original Message - From: "Jeff Slutzky" <[EMAIL PROTECTED]> To: "'Dirk Bremer (NISC)'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Tuesday, January 28, 2003 15:42 Subject: RE: socket application > I'm glad my question was inspiring. I am trying to get this to work on my > Win2000 Workstation and it just hanging, not erroring out or anything. I > tested your code on another SCO server and it works like a charm. What > platform did you test this on? I thank you again for your help. > Jeff, I tested both the sender and receiver scripts on Win2k boxes. No Unix available to play with. Dirk Bremer - Systems Programmer II - ESS/AMS - NISC St. Peters USA Central Time Zone 636-922-9158 ext. 8652 fax 636-447-4471 [EMAIL PROTECTED] www.nisc.cc ___ Perl-Win32-Users mailing list [EMAIL PROTECTED] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
RE: socket application
I'm glad my question was inspiring. I am trying to get this to work on my
Win2000 Workstation and it just hanging, not erroring out or anything. I
tested your code on another SCO server and it works like a charm. What
platform did you test this on? I thank you again for your help.
-Original Message-
From: Dirk Bremer (NISC)
Sent: Tuesday, January 28, 2003 3:11 PM
To: [EMAIL PROTECTED]
Subject: Re: socket application
- Original Message -
From: "Jeff Slutzky" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 28, 2003 13:13
Subject: socket application
> I am attempting to make a socket server running on a Win98 platform and
> have a socket client connecting from a SCO Unix platform. What happens
is
> that I start the server and it sits waiting, I then connect from the SCO
> server with the client socket app and I detect a connection on the
Windows
> box. What doesn't happen is the client sends a "Hello" string to the
> server and the server does not read what's going through the socket.
>
> sockets.pl - running on a Win98 box.
>
> use IO::Socket;
>
> my $sock = new IO::Socket::INET (LocalHost => '192.168.2.39', LocalPort
=>
> '7801', Proto => 'tcp', Listen => 1, Reuse => 1,);
> die "Could not create socket: $!\n" unless $sock;
> my $new_sock = $sock->accept();
> print "accept\n";
> while($new_sock) {
> print $_;
> }
> close($sock);
Jeff,
I played around with your code a bit, never having used sockets before, and
came up with this functioning version of your program.
my $Socket;
my $RDR = new IO::Socket::INET (LocalHost => 'XXX.XXX.XXX.XXX', LocalPort
=>'7801', Proto => 'tcp', Listen => 1, Reuse => 1);
die("Could not create socket: $!") unless($RDR);
while($Socket = $RDR->accept())
{
while (<$Socket>) {chomp; print(">$_<\n")}
}
close($RDR);
close($Socket);
To all,
Jeff's initial code inspired me to play around a bit with an idea I've had
for a while. I would like to able kill and then restart certain processes
on
another machine. Using code similar to above, I have tested it on the other
machine and it does receive messages sent from my machine. Both machines
are
Win2K. I would send predefined commands to the other machine to kill a
specific process, then update the programs on the other machines by an
external and manual process, and then would send other predefined commands
to restart the programs. I think I can handle sending and receiving the
messages and the restarting of the programs. The one piece of information I
will need is how to kill the processes on the other machine. This can be
done from the receiving socket program that will be executing on the other
machine. Both of the processes I am interested in killing run in separate
windows with specific window titles. Which is the best way to locate these
processes and then kill them? Note that neither of the processes on the
remote machine are written in Perl. Your suggestions will be appreciated.
Dirk Bremer - Systems Programmer II - ESS/AMS - NISC St. Peters
USA Central Time Zone
636-922-9158 ext. 8652 fax 636-447-4471
[EMAIL PROTECTED]
www.nisc.cc
___
Perl-Win32-Users mailing list
[EMAIL PROTECTED]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
___
Perl-Win32-Users mailing list
[EMAIL PROTECTED]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Re: socket application
- Original Message - From: "Gerber, Christopher J" <[EMAIL PROTECTED]> To: "'Dirk Bremer (NISC)'" <[EMAIL PROTECTED]> Sent: Tuesday, January 28, 2003 15:25 Subject: RE: socket application > Dirk, > > I had hacked together something like this in C at one point. I think I have > a copy of the source code at home. I'll see if I can find it and then we > can talk about turning it into Perl. If I can't find it, I should at least > be able to find the API calls. Are the processes that you're killing > regular apps, or services. (Services would be easier.) > > Chris > Chris, They are not services and written in the WinBatch scripting language that supports the creation of its own windows. They are not console windows per se, but similar. I have used something in Win32::GUI to locate a particular window by its title, but have no idea how to kill the window once it has been located. Dirk Bremer - Systems Programmer II - ESS/AMS - NISC St. Peters USA Central Time Zone 636-922-9158 ext. 8652 fax 636-447-4471 [EMAIL PROTECTED] www.nisc.cc ___ Perl-Win32-Users mailing list [EMAIL PROTECTED] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Re: socket application
- Original Message -
From: "Jeff Slutzky" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 28, 2003 13:13
Subject: socket application
> I am attempting to make a socket server running on a Win98 platform and
> have a socket client connecting from a SCO Unix platform. What happens is
> that I start the server and it sits waiting, I then connect from the SCO
> server with the client socket app and I detect a connection on the Windows
> box. What doesn't happen is the client sends a "Hello" string to the
> server and the server does not read what's going through the socket.
>
> sockets.pl - running on a Win98 box.
>
> use IO::Socket;
>
> my $sock = new IO::Socket::INET (LocalHost => '192.168.2.39', LocalPort =>
> '7801', Proto => 'tcp', Listen => 1, Reuse => 1,);
> die "Could not create socket: $!\n" unless $sock;
> my $new_sock = $sock->accept();
> print "accept\n";
> while($new_sock) {
> print $_;
> }
> close($sock);
Jeff,
I played around with your code a bit, never having used sockets before, and
came up with this functioning version of your program.
my $Socket;
my $RDR = new IO::Socket::INET (LocalHost => 'XXX.XXX.XXX.XXX', LocalPort
=>'7801', Proto => 'tcp', Listen => 1, Reuse => 1);
die("Could not create socket: $!") unless($RDR);
while($Socket = $RDR->accept())
{
while (<$Socket>) {chomp; print(">$_<\n")}
}
close($RDR);
close($Socket);
To all,
Jeff's initial code inspired me to play around a bit with an idea I've had
for a while. I would like to able kill and then restart certain processes on
another machine. Using code similar to above, I have tested it on the other
machine and it does receive messages sent from my machine. Both machines are
Win2K. I would send predefined commands to the other machine to kill a
specific process, then update the programs on the other machines by an
external and manual process, and then would send other predefined commands
to restart the programs. I think I can handle sending and receiving the
messages and the restarting of the programs. The one piece of information I
will need is how to kill the processes on the other machine. This can be
done from the receiving socket program that will be executing on the other
machine. Both of the processes I am interested in killing run in separate
windows with specific window titles. Which is the best way to locate these
processes and then kill them? Note that neither of the processes on the
remote machine are written in Perl. Your suggestions will be appreciated.
Dirk Bremer - Systems Programmer II - ESS/AMS - NISC St. Peters
USA Central Time Zone
636-922-9158 ext. 8652 fax 636-447-4471
[EMAIL PROTECTED]
www.nisc.cc
___
Perl-Win32-Users mailing list
[EMAIL PROTECTED]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Re: socket application
Jeff Slutzky wrote:
>
> I am attempting to make a socket server running on a Win98 platform and
> have a socket client connecting from a SCO Unix platform. What happens is
> that I start the server and it sits waiting, I then connect from the SCO
> server with the client socket app and I detect a connection on the Windows
> box. What doesn't happen is the client sends a "Hello" string to the
> server and the server does not read what's going through the socket.
>
> I'm attaching the code, and it is pretty plain jane. If anyone can point
> me in the right direction I would appreciate it.
>
> ++
> sockets.pl - running on a Win98 box.
>
> use IO::Socket;
>
> my $sock = new IO::Socket::INET (LocalHost => '192.168.2.39', LocalPort =>
> '7801', Proto => 'tcp', Listen => 1, Reuse => 1,);
> die "Could not create socket: $!\n" unless $sock;
> my $new_sock = $sock->accept();
> print "accept\n";
> while($new_sock) {
> print $_;
> }
> close($sock);
>
how about using the recv method on $new_sock:
$new_sock->recv($inbuf,$inbuf_length,0) or croak "$0 - can't recv: $!";
--
Alan F. Dickey - Interaction and Realization
http://www.intac.com/~afdickey
mailto:[EMAIL PROTECTED]
VOX: 908-273-3232 Cell: 908-334-0932
___
Perl-Win32-Users mailing list
[EMAIL PROTECTED]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
socket application
I am attempting to make a socket server running on a Win98 platform and
have a socket client connecting from a SCO Unix platform. What happens is
that I start the server and it sits waiting, I then connect from the SCO
server with the client socket app and I detect a connection on the Windows
box. What doesn't happen is the client sends a "Hello" string to the
server and the server does not read what's going through the socket.
I'm attaching the code, and it is pretty plain jane. If anyone can point
me in the right direction I would appreciate it.
++
sockets.pl - running on a Win98 box.
use IO::Socket;
my $sock = new IO::Socket::INET (LocalHost => '192.168.2.39', LocalPort =>
'7801', Proto => 'tcp', Listen => 1, Reuse => 1,);
die "Could not create socket: $!\n" unless $sock;
my $new_sock = $sock->accept();
print "accept\n";
while($new_sock) {
print $_;
}
close($sock);
socketc.pl - running on a SCO Unix server.
#!/usr/local/bin/perl
use IO::Socket;
my $sock = new IO::Socket::INET (PeerAddr => '192.168.2.39', PeerPort =>
'7801', Proto => 'tcp',);
die "Could not create socket: $!\n" unless $sock;
print $sock "Hello there\n";
close($sock);
+++
Thanks
_
Jeffrey L. Slutzky
___
Perl-Win32-Users mailing list
[EMAIL PROTECTED]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
