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

Re: [Freeciv-Dev] backgrounding civserver causes weird problems

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: garymoyer@xxxxxxxx, Greg Wooledge <wooledge@xxxxxxxxxxx>, "freeciv-dev@xxxxxxxxxxx" <freeciv-dev@xxxxxxxxxxx>
Subject: Re: [Freeciv-Dev] backgrounding civserver causes weird problems
From: Reinier Post <rp@xxxxxxxxxx>
Date: Sat, 28 Aug 1999 03:19:26 +0200

> That would be great, however it amplifies another: if you can't get the 
> console
> back how can any administative commands be issued?  e.g. saving the game.  
> Please
> see my previous email concerning cmdlevel.
> 
> I can add a commandline switch to run in daemon mode however the cmdlevel 
> issue
> needs to be resolved.

Yes.  Earlier versions of the cmdlevel patch (not in CVS) allowed cmdlevels
to be attached to AI players, so you could put

  set cmdlevel ctrl
  create operator
  set cmdlevel info

into .civserverrc, then start the game with

  civserver -r .civsrverrc & civclient -n operator localhost

or similar.  

PPS I had a weird idea to get around this: an /on command that allows commands
to be issued automatically on certain events.  I did a patch to implement it,
too.  The patch allows things like this:

  set cmdlevel ctrl
  on join set cmdlevel info

so only the first player to join gets control over the server.  There
are four events: join, leave, start, and quit.  The patch SEGVed on
commands that try to do something with a player that was just being
removed, besides I couln't see many other useful applications, and the
whole idea is a little freaky, so I stopped at that point.

> -- Gary

-- 
Reinier Post                                             rp@xxxxxxxxxx

Attachment: freeciv-jul18+on.diff-Nurd.gz
Description: application/gunzip


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