-
Notifications
You must be signed in to change notification settings - Fork 225
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
Vulnerable to similar screen sessions #27
Comments
same problem here. somehow got 2 screens running and all msm commands stopped working (problem for me because I crontab start/stop my server). Posting to follow to resolution :) |
I fixed this by getting the PID of the Java process after spawning the |
@PugTsurani That should get you going. |
Awesome! Thanks for the tip, @FabianN. |
I had similar problem when a server name includes another (I had "zavxmieux" and "zavxmieux-test"), I solved it setting Or, why not to filter grep output with SERVER_PATH instead of full SERVER_INVOCATION ? |
As seen in issue #23 (specifically this comment) MSM fails to stop servers when multiple screen sessions are found matching the expected name. Guards must be put in place to gracefully deal with this problem or eliminate it.
A solution may be to append salt data to the screen name on each start up, save that to file and check it subsequently. Or just be damn sure a screen session is dead when stopping servers.
The text was updated successfully, but these errors were encountered: