I'm spawning a couple of background processes in my Rails app, and have inserted checks to see if old processes (possibly from earlier runs of the app) are still around. If there are old processes, the app either kills them or lets them carry on with their work and desists from spawning even more processes. I use something like Process.kill(0, pid) to check if old processes are still alive.
Unfortunately, on the Heroku server this call always indicates that the process is dead. In short, I have no access to processes that I once spawned, although I have their pid stored in the db. I can neither kill them nor reliably find out if they are alive. This has lead to situations where I had to redeploy to a new Heroku process to get rid of background processes hanging around in the background. For my app to work, I simply need to be able to spawn, track and kill processes. Is there a workaround, or do you envision one for the future? I understand there are various security considerations, but it's not that complicated: let processes with the same uid do what they will with each other. For now, I've had to move back my app to my old server, which is otherwise so much less sexy than Heroku. Felix --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~----------~----~----~----~------~----~------~--~---
