I use a PsKill tool to remove XCOPY processes. Searching by Google will locate downloading sites.

Jie

-----Original Message-----
From: David Pattern [mailto:[log in to unmask]]
Sent: 01 October 2002 15:00
To: [log in to unmask]
Subject: Re: Processes failing to close on the server


Hi

The old Resource Kit for Windows NT4 used to come with a handy program
called "KILL.EXE" that's rather good at getting rid of unwanted processes -
so, simply running "KILL XCOPY" would terminate all the outstanding XCOPY
processes (although possibly include legitmate ones that are currently
running). There's some more info on the Microsoft site - e.g.
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q171773&

Also, you can specify the PID number if you just want to terminate a single
process. I find it comes in handy for killing rogue CGI Perl scripts that
are stuck, looping or just taken too damn long to run!

I'm not sure if the Resource Kit for Windows 2000 comes with a similiar
tool, or if the old NT4 one works under 2000. A quick search on
alltheweb.com brings up lots of possible places to download the tool from
(http://www.alltheweb.com/search?cat=ftp&cs=utf-8&ftype=4&q=kill.exe) - if
you do decide to download, make sure: it's from a reputable FTP site; you
run the download through a few virus scanners; and you test it on a
non-production server first! I'm *guessing* that Microsoft have made the
tool publically available, seeing as it's available on lots of reputable FTP
sites - if in doubt, try and hunt down a copy of the Resource Kit CD
instead.

You might also want to consider storing the file on a floppy, rather than
leave it sat on the server - I'm sure a (cr|h)acker could spend a happy
afternoon using it to kill random process! :S

If you are happy leaving it sat on the server, you could probably knock up a
batch file and use AT to automatically run every couple of hours, killing
off the rogue processes.

Just an idea and don't blame me if it ends up deleting every single file on
the server!

regards
Dave Pattern
INHALE Project (http://inhale.hud.ac.uk)


-----Original Message-----
From: Shen, Dr J. [mailto:[log in to unmask]]
Sent: 01 October 2002 12:14
To: [log in to unmask]
Subject: Re: Processes failing to close on the server


Hi Andy,

It happened on our server as well. The problem occurs when a zip file is
updated. If a zip file is removed and another one (e.g. an updated version)
is attached immediately (within the same editing session without leaving the
editing page), then an XCOPY process will be created and it will not kill
itself. When there are enough XCOPY processes on the system, Bb service will
halt. One way to avoid this is to remove the zip file first and then attach
the updated version in a separate editing session. However once a zip file
has caused such a problem, simply removing it will also create XCOPY. As I
understand from discussions on a US list, this is a Bb problem, but Bb
support seems not being able to understand the real cause of the problem. No
one knows if this problem will be corrected in version 6 either. I just
check our server regularly and kill any XCOPY processes.

Jie