--kill a process that has been running for /x/ seconds, minutes, or hours
Current Version: 18.104.22.168 - DOWNLOAD NOW
find a bug? report a bug!
What's it do?
I recently redesigning the company for which I work's website. With that, I was asked to set up a quoting system that would take values from a web form, save them to a database, and dump those values into an Excel spreadsheet, do some major calculations, then spit out some other values (total costs) back into the database, and display them back to the client.
Well, all of that's working just great... except that, if the client cancels the page before the calculations are done, Excel hangs in task manager. Enter my search for a program that would search task manager for a specified process that has been running for a specified amount of time, and kill it -- my search ended, still empty handed...
But hey, I'm a programmer... why not write one? -- so i did.
And here's my result.
KillProc is an application that does just that... it kills a specified process that has been running for a specified amount of time.
KillProc.exe /p:[process name] /t:[time to wait] [/s] [/m] [/h] [/?]
/s - Time interval in seconds (default)
/m - Time interval in minutes
/h - Time interval in hours
/? - Shows help screen
Things to note:
-The first time interval tag called will be used -- if you use "/s /m," time interval will be in seconds
-The process name is CaSE InSenSiTIve. -- some processes (EXCEL.EXE) for example, are in all caps, while others (notepad.exe) are all lowercase. either way, you don't have to worry about it
-The defined process does not need, but can have the ".exe" extension.
Typical disclaimer applies:
This software is provided by the copyright holder and contributors "as is" and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall the copyright owner or contributors be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this software, even if advised of the possibility of such damage.
Basically, I am not responsible for the way this application is used, nor can I ensure that no damage will be caused by using this program. Don't use it to kill "explorer.exe," for example. Use it the way you would use TASKKILL, and you'll be alright.