Windows pid kill

[Fairlight]

The honourable and venerable Richard Kreiss spoke thus:
> After doing some research, I found there is a way to get the PID for a
> windows processes, at least in terminal server.

I use Iarsn Taskinfo.  It is a wonderfully souped up task manager and
resource monitor that provides a plethora of information about every
process and thread on the system.  

It also has buttons to pause, close, and terminate programs.  The close is
gentle, and will not erradicate "hung" processes.  The terminate is pretty
much analogous to kill -9 in unix...terminate with prejudice, and you're
warned about the likelihood of lost unsaved data and potential system
instability (the latter really depending on -what- you kill--killing clerk
or report would not cause any, killing a device driver would).

It's my tool of choice for managing processes and monitoring system
resources.

> Might I assume that if clerk in not in update on a record the file will be
> closed and there should be no damage to the file.

It'd just be open for reading.  The process holding the file open should
lose its lock(s) on the file and no harm done.

> However, what about if one of these sessions is in update mode on a record,
> how high is the probability that the file will be damaged?

Unless it's in mid-write, I'd say negligible.  I concur with Ken--no more
harsh than kill -9 would be.

> One of my client's needs to backup his system and finds that some of the
> terminal server sessions have timed out while running clerk and cannot
> backup the open file(s).  Thus the need to kill these processes.

It'd probably be easier with Taskinfo.  Highlight and click, rather than
much typing.  Task Manager can do this as well, but it's just not robust
enough for me to like.

mark->
-- 
"Moral cowardice will surely be written as the cause on the death
certificate of what used to be Western Civilization." --James P. Hogan