Zandronum Chat on our Discord Server Get the latest version: 3.2
Source Code

View Revisions: Issue #2157 All Revisions ] Back to Issue ]
Summary 0002157: Unique crash report file name for the linux server hosts
Revision 2015-04-25 13:50 by Edward-san
Description Jenova mentioned an issue with the actual linux crashlog system.

In host server systems like bestever, all the games which are hosted are run with the same zandronum-server executable. If a crash happens in a game, a 'zandronum-crash.log' is saved in the same place as the server executable. If another crash happens from another game, the first crash will be overwritten by the second, making the investigation impossible.




What was suggested as the unique name would be using the crash time, like 'zandronum-crash-04_02_2015-00_40_02.log', though suggestions are welcome.
Revision 2015-04-25 10:03 by cobalt
Description Jenova mentioned an issue with the actual linux crashlog system.

In host server systems like bestever, all the games which are hosted are run with the same zandronum-server executable. If a crash happens in a game, a 'zandronum-crash.log' is saved in the same place as the server executable. If another crash happens from another game, the first crash will be overwritten by the second, making the investigation impossible.




What was suggested as the unique name would be using the crash time, like 'zandronum-crash-04_02_2015-00_40_02.log', though suggestions are welcome.
Revision 2015-04-01 22:50 by Edward-san
Description Jenova mentioned an issue with the actual linux crashlog system.

In host server systems like bestever, all the games which are hosted are run with the same zandronum-server executable. If a crash happens in a game, a 'zandronum-crash.log' is saved in the same place as the server executable. If another crash happens from another game, the first crash will be overwritten by the second, making the investigation impossible.




What was suggested as the unique name would be using the crash time, like 'zandronum-crash-04_02_2015-00_40_02.log', though suggestions are welcome.






Questions or other issues? Contact Us.

Links


Copyright © 2000 - 2025 MantisBT Team
Powered by Mantis Bugtracker