empire/empserver
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update change log again for 4.3.30

Browse source
This commit is contained in:
Markus Armbruster 2012-04-29 20:29:04 +02:00
parent 540526a140
commit fe33d92ed0
2 changed files with 22 additions and 16 deletions
Download patch file Download diff file Expand all files Collapse all files

19
doc/CHANGES4.X
View file

@ -1,15 +1,18 @@
Changes to Empire 4.3.30 - Thu Apr 26 18:14:49 UTC 2012 Changes to Empire 4.3.30 - Sun Apr 29 18:27:41 UTC 2012
* Fix arm to require nuke and plane to be in the same sector. A
remote nuke got teleported to its plane when the plane moved.
Broken in 4.3.3.
* Change login command kill (used by client option -k) to kill less * Change login command kill (used by client option -k) to kill less
ruthlessly: send a flash message and try to flush output, exactly ruthlessly: send a flash message and try to flush output, exactly
like a server shutdown does. like a server shutdown does.
* Fix server shutdown to wait for player threads to reach a safe * Fix server shutdown to wait for player threads to reach a safe
state. Without that, we could fail to update the treasury, record state. Before, player threads raced with shutdown, and failed to
play time, and write log entries. The old code is racy. It goes update the treasury, record play time, and write log entries when
back to Empire 2. It was patched in 4.2.10, 4.2.12, 4.2.20, 4.3.6, they lost. Bug goes back to Empire 2. Patched partially or
4.3.10 and 4.3.23, but the core problem remained unaddressed. unsuccessfully in 4.2.10, 4.2.12, 4.2.20, 4.3.6, 4.3.10 and 4.3.23.
* When shutdown aborts a command, the terminating player thread could The race was hard to lose in practice, until an unrelated
still get stuck sending output, and thus lose the race just "simplification" in 4.3.32 could get player threads stuck sending
mentioned. Broken in 4.3.23. output after shutdown aborted a command.
* Idle timeout changes: * Idle timeout changes:
- The grace period for clients to complete login and logout is now - The grace period for clients to complete login and logout is now
separate from the idle timeout. Configurable with new econfig separate from the idle timeout. Configurable with new econfig

19
info/Empire4.t
View file

@ -7,18 +7,21 @@ new Empire4 Server. This outlines the various changes and how they
will affect you, the player. These were coded as the Wolfpack project, will affect you, the player. These were coded as the Wolfpack project,
and bug-reports should be sent to <wolfpack@wolfpackempire.com>. and bug-reports should be sent to <wolfpack@wolfpackempire.com>.
.NF .NF
Changes to Empire 4.3.30 - Thu Apr 26 18:14:49 UTC 2012 Changes to Empire 4.3.30 - Sun Apr 29 18:27:41 UTC 2012
* Fix arm to require nuke and plane to be in the same sector. A
remote nuke got teleported to its plane when the plane moved.
Broken in 4.3.3.
* Change login command kill (used by client option -k) to kill less * Change login command kill (used by client option -k) to kill less
ruthlessly: send a flash message and try to flush output, exactly ruthlessly: send a flash message and try to flush output, exactly
like a server shutdown does. like a server shutdown does.
* Fix server shutdown to wait for player threads to reach a safe * Fix server shutdown to wait for player threads to reach a safe
state. Without that, we could fail to update the treasury, record state. Before, player threads raced with shutdown, and failed to
play time, and write log entries. The old code is racy. It goes update the treasury, record play time, and write log entries when
back to Empire 2. It was patched in 4.2.10, 4.2.12, 4.2.20, 4.3.6, they lost. Bug goes back to Empire 2. Patched partially or
4.3.10 and 4.3.23, but the core problem remained unaddressed. unsuccessfully in 4.2.10, 4.2.12, 4.2.20, 4.3.6, 4.3.10 and 4.3.23.
* When shutdown aborts a command, the terminating player thread could The race was hard to lose in practice, until an unrelated
still get stuck sending output, and thus lose the race just "simplification" in 4.3.32 could get player threads stuck sending
mentioned. Broken in 4.3.23. output after shutdown aborted a command.
* Idle timeout changes: * Idle timeout changes:
- The grace period for clients to complete login and logout is now - The grace period for clients to complete login and logout is now
separate from the idle timeout. Configurable with new econfig separate from the idle timeout. Configurable with new econfig