-
Notifications
You must be signed in to change notification settings - Fork 631
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doesn't follow forks? #708
Comments
@haydenflinner is this still an issue? |
Well, did you do anything that would have fixed it? I don't see anything in the commit history since I posted it that would have helped. Although in hindsight one workaround is
|
I’m just trying to help out the maintainer by doing some issue triage 🙂 |
Maybe due to #779? That issue has been addressed in |
This would probably be the perfect fix. Running in separate process group and killing that is perfect. I forgot about this tool but may need it again in the near future, I'll use your fork if so, that is the proper way to do it! |
I have a procfile that looks like this:
When I run it with Foreman, the gtstores are still visible with
pgrep store
, and their pids are a little bit higher than the PIDs that Foreman claims to have seen.When I run the same procfile with
honcho
, everything works fine; the processes are killed at the end as expected.The text was updated successfully, but these errors were encountered: