Zandronum Chat on our Discord Server Get the latest version: 3.2
Source Code
My View | View Issues | Change Log | Roadmap | All Projects Issue Support Ranking | Rules | My Account
  

View Revisions: Issue #3324 [ All Revisions ] [ Back to Issue ]
Summary 0003324: RCon client process stays alive after RCon fails and init is finished, doesn't exit normally after error
Revision 2017-11-03 12:44 by WubTheCaptain
Steps To Reproduce Start Doomseeker in RCon client mode, preferably from a terminal for stdout:

$ doomseeker --rcon
[12:23:28] Starting Doomseeker. Hello World! :)
...
[12:23:28] Starting RCon client.


Try an engine which doesn't support RCon (currently as of writing, anything but Zandronum). The server address and password don't seem to matter, I've set both to blank (null).

The following two lines (ignoring the timestamp) should be appended to stdout:

[12:23:30] Init finished.
================================


An error should also be printed about lack of support.

Notice the process is still alive but nothing is happening. This is verifiable with pgrep (GNU/Linux):

$ pgrep doomseeker
28567


Repeating these steps will create more processes, which can be found with pgrep.

Ctrl + C (^C) will forcefully terminate the process.
Revision 2017-11-03 12:44 by WubTheCaptain
Steps To Reproduce Start Doomseeker in RCon client mode, preferably from a terminal for stdout:

$ doomseeker --rcon
[12:23:28] Starting Doomseeker. Hello World! :)
...
[12:23:28] Starting RCon client.


Try an engine which doesn't support RCon (currently as of writing, anything but Zandronum). The server address and password don't seem to matter, I've set both to blank (null).

The following two lines (ignoring the timestamp) should be appended to stdout:

[12:23:30] Init finished.
================================


An error should also be printed about lack of support.

Notice the process is still alive but nothing is happening. This is verifiable with pgrep (GNU/Linux):

$ pgrep doomseeker
28567


Repeating these will create more processes, which can be found with pgrep.

Ctrl + C (^C) will forcefully terminate the process.
Revision 2017-11-03 12:38 by WubTheCaptain
Steps To Reproduce Start Doomseeker in RCon client mode, preferably from a terminal for stdout:

$ doomseeker --rcon
[12:23:28] Starting Doomseeker. Hello World! :)
...
[12:23:28] Starting RCon client.


Try an engine which doesn't support RCon (currently as of writing, anything but Zandronum). The server address and password don't seem to matter, I've set both to blank (null).

The following two lines (ignoring the timestamp) should be appended to stdout:

[12:23:30] Init finished.
================================


An error should also be printed about lack of support.

Notice the process is still alive but nothing is happening. This is verifiable with pgrep (GNU/Linux):

$ pgrep doomseeker
28567


Ctrl + C (^C) will forcefully terminate the process.




Questions or other issues? Contact Us.

Links

Copyright © 2000 - 2025 MantisBT Team
Powered by Mantis Bugtracker