[shogi-server] Support listening on IPv6 addresses Thanks to mizar for a patch. (Closes #40822)
Terminate threads of players so that the server shuts down (Closes #38544)
[shogi-server] Create a directory for a PID file. (Closes #38546) To put a PID file such as /var/run/shogi-server/shogi-server.pid, if directories do not exist, they will be created recursively.
* [shogi-server] Support a graceful shutdown. (Closes #38544) A file named "STOP" in the base directory prevents the server from starting new games including Floodgate matches.
Fix #36821: Allow to customize maximum lenght of a login indentifier
[shogi-server] Enhance capability of Floodgate configuration file - New parameter: Max_Moves, defined in the CSA protocol ex. set Max_Moves 256 - New parameter: Least_Time_Per_Move, defined in the CSA protocol ex. set Least_Time_Per_Move 0 - Proposed messages distributed to each player upon starting a new game will include Max_Moves as well as Least_Time_Per_Move. - CSA files produced by the server will include settings of Max_Moves and Least_Time_Per_Move in comment lines as follows: 'Max_Moves:256 'Least_Time_Per_Move:0 - The official Shogi-server on wdoor.c.u-tokyo.ac.jp will be running with different parameters, depending on game names. a) Max_Moves will be 256 for floodgate-600-10 games; otherwise, 0. b) Least_Time_Per_Move will be 0 for floodgate-600-10 games; otherwise 1. (Closes: #35839)
[shogi-server] shogi-server, shogi_server/{command,game_result,player}.rb: The change at 2014-10-13 was not worked as expected. Reworked. A player, attempting to login with the current live player stalling for more than a day, can forcibly override the current player.
Merge branch '201410-maxmoves' Conflicts: changelog shogi_server.rb
Update various documentations
Apply CSA Protocol V1.2.1 for MAX_MOVES
New feature: Zero least time per move. New command line option: --least-time-per-move n
Merge remote-tracking branch 'origin/wdoor-stable' Conflicts: changelog
Ruby 2.0.0 or later is recommended to use with shogi-server since Ruby 1.8 reached its End-of-Life on the end of July, 2014.
[shogi-server] A player, attempting to login with the current live player stalling for more than a day, can forcibly override the current player.
New feature: max moves New command line option: --max-moves n
Enhanced syntax of Floodgate time configuration file. Now it supports "set sacrifice <player_id>" It sets a sacrificed player for a specific Floodgate game. ex. set sacrifice gps500+e293220e3f8a3e59f79f6b0efffaa931
* [shogi-server] - shogi-server: any bind addresses, ruby attempts to listen on both "0.0.0.0" and "::". Specifying "::" on Linux leads to listen on both IPv4 and IPv6, which results in a warning message saying "Address already in use - bind(2)".
* [shogi-server] - shogi-server: Previously, reloading in daemon mode failed on ruby 1.9.3p194. This issue has been fixed.
Merge remote-tracking branch 'origin/wdoor-stable' Conflicts: changelog
Rleased: Revision "20131104"