kill

When an application's process is killed, its activity stack is saved. Then when the application is restarted, all my activities resume and run into null pointers. Rather than modify every activity to accommodate this event, I would rather just have my application start with the base activity and not try to re-create the activity stack. Is this possible? I know about Intent.FLAG_ACTIVITY_CLEAR_TOP, but as I understand that will only kill activities after they have been re-created. EDIT: is clearTaskOnLaunch what I want? I've added it to my default activity, but am seeing no effect. But this

I see a lot of connections are open and remain idle for a long time, say 5 minutes. Is there any solution to terminate / close it from server without restarting the mysql service? I am maintaining a legacy PHP system and can not close the connections those are established to execute the query. Should I reduce the timeout values in my.cnf file those defaults to 8 hours? # default 28800 seconds interactive_timeout=60 wait_timeout=60 Manual cleanup: You can KILL the processid. mysql> show full processlist; +---------+------------+-------------------+------+---------+-------+-------+--------------

Is there a way to ensure all created subprocess are dead at exit time of a Python program? By subprocess I mean those created with subprocess.Popen(). If not, should I iterate over all of the issuing kills and then kills -9? anything cleaner? You can use atexit for this, and register any clean up tasks to be run when your program exits. atexit.register(func[, *args[, **kargs]]) In your cleanup process, you can also implement your own wait, and kill it when a your desired timeout occurs. >>> import atexit >>> import sys >>> import time >>> >>> >>> >>> def cleanup(): ... timeout_sec = 5 ... for

How do I kill the last spawned background task in linux? Example: doSomething doAnotherThing doB & doC doD #kill doB ???? There's a special variable for this in bash: kill $! $! expands to the PID of the last process executed in the background. You can kill by job number. When you put a task in the background you'll see something like: $ ./script & [1] 35341 That [1] is the job number and can be referenced like: $ kill %1 $ kill %% # Most recent background job To see a list of job numbers use the jobs command. More from man bash : There are a number of ways to refer to a job in the shell. The

I have a Python script that imports a large CSV file and then counts the number of occurrences of each word in the file, then exports the counts to another CSV file. But what is happening is that once that counting part is finished and the exporting begins it says Killed in the terminial. I don't think this is a memory problem (if it was I assume I would be getting a memory error and not Killed ). Could it be that the process is taking too long? If so, is there a way to extend the time-out period so I can avoid this? Here is the code: csv.field_size_limit(sys.maxsize) counter={} with open("