English (United Kingdom)French (Fr)Deutsch (DE-CH-AT)
Random Thumbnail
Who Is Online?
We have 155 guests online
Home Descent 3 Descent 3 dedicated server tool for Windows Console and Logging
Most Recent
Featured Articles
Joomla 1.5 Featured Articles
Home Descent 3 Descent 3 dedicated server tool for Windows Console and Logging
English (United Kingdom)French (Fr)Deutsch (DE-CH-AT)
Console and Logging E-mail
User Rating: / 7
Descent 3 - Descent 3 dedicated server tool for Windows
Written by Thomas   
Saturday, 03 October 2009 21:57

The configuration window Console and Logging lets you configure the remote console of your dedicated Descent 3 servers and the servers' logging behaviour.

It is opened from the button Console and Logging... in the server configuration dialog window.

D3Server_console_and_login01NewThe Remote console password is the password used for the remote console. When a dedicated server is created this password is set to the one defined in the global options.

Remote console port defines the TCP port used for the dedicated server's remote console, which is basically a telnet server. You can connect to it with any telnet client. When more than one dedicated Descent 3 server is hosted on the same machine each server must have its own unique TCP port. The dedicated server provides a remote console (telnet server) even if Allow remote console in its server configuration is switched off. That's why this port must be provided independant of whether remote console access is allowed or not. D3Server3 needs the remote console to control your dedicated Descent 3 servers.

The setting Log player names and IPs enables the server tool to query the dedicated Descent 3 server regularly for current player names and to store this information in a file. The file can be found in the folder "log" in D3Server3's installation directory. The file is called "PlayerInfo.txt". Together with each player's nickname (pilot name) an array of IP addresses is stored if the player connects from more than just one address.

D3Server3 keeps player information in the file PlayerInfo.txt for 3 months before it starts removing less recent entries. The file is a normal text file and can be opened with any text editor.

Requesting the player information from a dedicated Descent 3 server regulary can cause the server to crash when more than 10 players are in the game. The amount of players who can safely play in a server without crashing it while "Log player names and IPs" is active in D3Server may vary due to many other factors like CPU speed, amount of CPUs, and memory of the host machine.

D3Server3 can log the remote console communication with the Descent 3 remote console server and has several options to control the details. A dedicated Descent 3 server created and started by the server tool D3Server3 always has a remote console. The remote console server is created independant of the server configuration setting "Allow remote console".

D3Server_console_and_login02NewLog output to file enables the logging of the remote console communication. If off, nothing is logged.

Log all output switches on the verbose mode of the remote communication logging. Without this setting several events are not stored in the log file. The benefit of having Log all output on is that most of the remote console output shows up in the log file. The benefit of disabling this setting is a smaller log file.

Use timestamps prepends every line in the log file with a date and timestamp. The state of this setting is ignored if Logtext is used for data logging, because Logtext is controlled by its own configuration file.

Use Logtext DLL tells the server tool to look for and use the direct link library (DLL) logtext.dll. Logtext provides extensive data logging options controlled by a configurable Windows ini file, like automatic log file rotation, compression, and deletion. Note that the setting "Use timestamps" is ignored by Logtext.

The behaviour of Logtext is controlled by the file "logtext.ini" in the folder where D3Server3 has been installed. The distribution package of the server tool is shipped with a preconfigured version of this file.

The standard settings store the remote console communication output in a weekly file, keep 5 of these files uncompressed, compress 30 less recent versions, and use use the compression of Windows's file system NTFS, which doesn't require any decompression software like WinZip. If D3Server3 runs on a FAT partition the compression method GZip is ued.

With these default rotation settings the file logtext.ini included in the D3Server3 package stores 30 weeks of remote console communication output.

When a dedicated server starts and also whenever it changes a level in a multi-level mission D3Server3 can automatically send remote console commands to it. Enter one remote console command at a time in the text field "Remote console auto command" and press the "Add" button to add the command to the list.

To remove one or more commands again, first select it/them in the list and then press the "Remove" button.

The Ok button closes the "Console and Logging" window and applies the changes.

Cancel closes the "Console and Logging" window but discards the changes.

The button Online Help opens a browser window with this web page.

Last Updated on Sunday, 16 January 2011 16:42
You need to login or register to post comments.
Discuss this item on the forums. (0 posts)
Discuss (0 posts)