Issues booting servers after unclean shutdowns cause issues with port binds remaining after processes have been cleared would someone be able to throw in a smart method for
fuser -k -n tcp ${PORT}
potentially?
We could define the launch port in a new version of the config. This would be added to the bukkit runtime arguments. http://wiki.bukkit.org/CraftBukkit_Command_Line_Arguments
Since the port bind is created as root for this instance you cant clear ports unless you're a root user. This causes problems with allowing a multi tenant server to handle their own port bind issues.
Issues booting servers after unclean shutdowns cause issues with port binds remaining after processes have been cleared would someone be able to throw in a smart method for fuser -k -n tcp ${PORT} potentially? We could define the launch port in a new version of the config. This would be added to the bukkit runtime arguments. http://wiki.bukkit.org/CraftBukkit_Command_Line_Arguments
Since the port bind is created as root for this instance you cant clear ports unless you're a root user. This causes problems with allowing a multi tenant server to handle their own port bind issues.