tchize wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Mark Wedel a ?crit : > >> >> All in all, seems a lot simpler to just restart the server than try >> to sort all of this out. >> > Agree. However, if i understand well, the problem of kari Pahula is to > handle it all from command line in case of package upgrade. That mean > players get kicked out from a local command. May be we should have > server react to specific signal so it give all players something like > 2 minutes delay to log off, warn them, and refuses new connections > with an explanatory message. Then server will then be shutdown, > install script will replace maps / archetypes / whatever is new and > restart the server.
IIRC, this could be sort of possible by using the forbid file. I'm not sure that the timing is fine enough right now to get it down to the minute, but that could be done. That said, having the server take sigusr1 or something to do that action wouldn't be that hard. It probably just need a few lines of code. It is probably also easier if the assumption that an outside process will restart it. > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.1 (GNU/Linux) > Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org > > iD8DBQFEJtqCHHGOa1Q2wXwRAs/PAKDTavMT9+scqw1ljML223viWTwnTQCeMac4 > Ub1dBunJ8rXTvpG+0nTczNo= > =bzB+ > -----END PGP SIGNATURE----- > > > _______________________________________________ > crossfire mailing list > crossfire@metalforge.org > http://mailman.metalforge.org/mailman/listinfo/crossfire _______________________________________________ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire