Complete.Org: Mailing Lists: Archives: freeciv-dev: August 1999:
[Freeciv-Dev] backgrounding civserver causes weird problems
Home

[Freeciv-Dev] backgrounding civserver causes weird problems

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: "freeciv-dev@xxxxxxxxxxx" <freeciv-dev@xxxxxxxxxxx>
Subject: [Freeciv-Dev] backgrounding civserver causes weird problems
From: Gary Moyer <garymoyer@xxxxxxxx>
Date: Sat, 21 Aug 1999 23:28:19 -0700

I've noticed that if the server is backgrounded (and nohup'd) the server
hangs the next time input occurs on the same tty on which the game was
started.

Why would you want to background/nohup the server?  If a new game is
started and you're not sitting at the console on which the game is being
played.  Ideally you should be able to control the game remotely via
cmdlevel.

I looked at sniff_packets() and it adds descriptor 0 to the file
descriptor set which is used by select().  Isn't there a programatic way
of determining if the process has been nohup'd and essentially not
adding this descriptor to the descriptor set for use by select()?  This
could be done by checking to see if SIGHUP is attached to a signal
handler and if so not adding it?

Assuming cmdlevel was sticky (which it isn't -- see my previous email)
the game admin should be able to control all aspects of game play
remotely.

Any thoughts?

-- Gary


[Prev in Thread] Current Thread [Next in Thread]