Skip to content
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

Hard Stop Server SHOULD NOT kills all SA-MP servers processes #6

Open
Maxelweb opened this issue May 7, 2018 · 0 comments
Open

Hard Stop Server SHOULD NOT kills all SA-MP servers processes #6

Maxelweb opened this issue May 7, 2018 · 0 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@Maxelweb
Copy link
Owner

Maxelweb commented May 7, 2018

Actually, the Hard Stop Server button kills all the running sa-mp server processes named samp03svr and that's a problem for those running multiple servers in the same host.
Many requests are focused on changing this feature so that Hard Stop Server would only stop the current server selected.

In my opinion, the use of the PID to kill the process should not do the trick, because the PID could be associated to another running process, if someone already closes the sa-mp server manually.

In facts, you can still shutdown/close the server using /rcon exit in game.

A working way would be to rename the samp03svr application to samp03svr_shortRandomString so that the process comes with a unique name and there would not be any coincidences.

If someone has a better solution or a simpler alternative, please reply to this issue or in the sa-mp thread.

@Maxelweb Maxelweb added enhancement New feature or request help wanted Extra attention is needed labels May 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant