[Gandalf Parker]

Originally posted by Esben Mose Hansen:
The idea with one account pr. game is wonderful for play-by-email games. But I wouldn't want to do that from a CGI-interface: Creating accounts must for obvious reasons involve at least a sudo root operation. I would never let a CGI-script anywhere near that kind of power. Perhaps a chroot'ed approach could be found allowing for the one-accout-for-each-game approach.

True enough. Actually Ive done it in the past without sudo using a passed file as a work around. CGI creates a file with the account info. CRON reads it, checks it for possible abuse info, then creates the account with the info. But in general it is considered a thing to avoid.

Of course it wouldnt be much to a system to go ahead and make 100 or so such accounts then just roll the games thru them as needed.

As for storing game info, I use a mysql database. In there, I can do pretty much anything I want, without comprimising security. I could, e.g. store a backup for .2h files if I wished...

Well pros and cons. SQL has its own drawbacks. Even in security. But then everyone should tends to know and handle the problems for their favorite softwares which is really the right way to go.

Another thing: Maybe it's just Sunday, but interest in this server has been quite low: Exactly one game has been created. For the current load, TCP/IP is DEFINITELY the way to go. Much easier to build/adminster than mail, and any server could run less than 5 games without sweating.

When I saw the memory load it required I was scared away from that direction. But later I got up the nerve to start 2 games at the same time and saw that it handled librarys well. Most of what it loads does not get loaded for each server.