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.
Actually, the
Hard Stop Serverbutton kills all the running sa-mp server processes namedsamp03svrand 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 Serverwould 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.
A working way would be to rename the
samp03svrapplication tosamp03svr_shortRandomStringso 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.