kill

I have a parallelized automation script which needs to call many other scripts, some of which hang because they (incorrectly) wait for standard input or wait around for various other things that aren't going to happen. That's not a big deal because I catch those with alarm . The trick is to shut down those hung grandchild processes when the child shuts down. I thought various incantations of SIGCHLD , waiting, and process groups could do the trick, but they all block and the grandchildren aren't reaped. My solution, which works, just doesn't seem like it is the right solution. I'm not

What's the best way to kill a process in Java ? Get the PID and then killing it with Runtime.exec() ? Use destroyForcibly() ? What's the difference between these two methods, and is there any others solutions ? Derlin If the process you want to kill has been started by your application Then you probably have a reference to it ( ProcessBuilder.start() or Runtime.exec() both return a reference). In this case, you can simply call p.destroy() . I think this is the cleanest way (but be careful: sub-processes started by p may stay alive, check http://bugs.sun.com/bugdatabase/view_bug.do?bug_id

if you have an android app that has more than one Activity, and Activity A starts B, so if Activity b crashes the process is killed but is revived by android OS and starts Activity A again instead of just shutting down the app, why ? You're complaining that Android will attempt to recover your app's state gracefully after a crash? ;) This is the result of Android's resource management and the Activity lifecycle at work. Keep in mind that a single task can be composed of a number of Activities that may span several processes or apps. As outlined here: http://android-developers.blogspot.com/2010

Good Day, I have a .bat file that run a specific application then after 5 seconds it will close/kill it. I having right now due to it successfully open the application thought when the app opens it will not execute the remaining commands unless I manually close the app. Here is my code: cd "C:\Program Files (x86)\Aspera\Point-to-Point\bin\" asperascp.exe sleep 5 taskkill /IM asperascp.exe /f I also try removing the sleep command. cd "C:\Program Files (x86)\Aspera\Point-to-Point\bin\" asperascp.exe taskkill /IM asperascp.exe /f But it will have same output it will not execute the remaining

I'm uncertain whether to use pty.fork() or os.fork() when spawning external background processes from my app. (Such as chess engines) I want the spawned processes to die if the parent is killed, as with spawning apps in a terminal. What are the ups and downs between the two forks? The child process created with os.fork() inherits stdin/stdout/stderr from parent process, while the child created with pty.fork() is connected to new pseudo terminal. You need the later when you write a program like xterm: pty.fork() in parent process returns a descriptor to control terminal of child process, so you