Forums

I'm aware that there is currently no way to kill processes. I (foolishly) started testing a program which would text my phone once a minute. I killed the console when I had enough yet my phone is still getting text messages. Luckily, the program should only run for 30 more minutes so I only have 30 more texts to receive. Lesson learned.

Is there a workaround to this? Why is my program still running if I killed the console? Is there a way to make sure this doesn't keep running if there is a next time?

Did reloading the webapp do anything? Or was it some other random python script located elsewhere?

Or if it shows up on the "Schedule" tab with a process id, you can start a new bash and run kill with that process id.

It was a random python script I was fooling with that I clicked save and run on. Is there any way to keep that from happening again or should I just be more careful?

Normally processes should die when you kill the console, but sometimes our underlying Linux OS does something weird and they don't. There are some virtualisation hacks we could do to fix this, but all of them come with performance, price or other penalties.

One thing that might help -- if you hit Control-C in the console to kill your process instead of killing it from the "Consoles" tab, that should be more reliable.