Linux server STDIN required?

[Mxyzptlk]

With etded.x86 we're able to run a server without STDIN (or screen). Using etqwded.x86 I've noticed that STDOUT/STDERR now is flooded with 'empty read' lines when trying to run it in the background. I've tried different in_tty settings and still no-go.

Anyone have any idea how to make this puppy run in the background without using screen?

[escapedturkey]

nohup ./etqwded.x86 +set net_serverDedicated 1 +set in_tty 0 +set net_ip INSERTIPADDRESSHERE +set net_port 27733 +set fs_basepath /home/username/quakewars +set fs_savepath /home/username/quakewars +set fs_devpath /home/username/quakewars +set net_serverPunkbusterEnabled 1 +set fs_game "" +set fs_game_base base +set logfile games.log +exec server.cfg &

:cool:

[Mxyzptlk]

Thanks but that doesn't redirect stdout to a file. Also 'logfile' is, according to the version of etqwded.x86 I have, a number-value CVAR:

+set logFile "1" +set logFileName "console.log" +set logTimeStamps "1"

Works fine, but again, stdout capturing gets corrupted/flooded with nothing but read errors after launching.

As it stands now, it looks like redirecting stdout/stderr and stdin to /dev/null is required for a clean background launch.

[escapedturkey]

The output of the server starting should go to: nohup.out

For better logging, please try this in your server.cfg:

seta logFile "2" // 0-no logging 1-buffer log 2-flush after each print - 1 should be fine in most cases
seta logFileName "qwconsole.log" // name of logfile

:cool:

[Mxyzptlk]

Take a look at your nohup.out, what does it show after the server starts. After about 1000 lines of output, I see a flood of "empty read" lines.