Previous game went into /dev/null. I feel very bad about it and want to say HUGE I AM SORRY to guy who played as "Trikky Transport" and spend much of time to build rails & networks. Game was going to be interesting, but I've screwed it up when was simply restarting server with hands.
Explanation: Usually, when I start server via "./sim120 -server 13353 ...blahblah arguments ..blahblah -load savegame.sve", it loads savegame.sve file and start running that game, giving remote access. I had to run it with -load argument only once, but i didn't knew it. Server usually stores savegame file (to continue from) as network-savegame13353.sve in simutrans/ directory, but it continues only if i don't use -load parameter. But i did. So it took savegame.sve (initial map, w/o anything on it!) and overwrites latest savegame, thus deleting it permanently. I didn't read instructions deeply, so I'm such a douche. Again. I am sorry, I cann't recover game at all. It's not like file was deleted and I could undelete it with e2undelete utility or similar. It was overridden by another data and completely lost (I guess).
So what i'm working with. I work on multi-instance server managing script working as init.d service. I'll have simutrans directories at
"simutrans/runs/", each of which contains everything about server instances: server configuration, init savegame, running savegame, backup(!) savegames, maybe some auto-generated info pages automatically hosted by apache2 webserver (it's for server_info parameter containing info url), pak data, initial map, etc etc etc. Currently it's still nothing, but i'm putting together basic config parameters.
Having 2 server maps on Debian64, it looks like this (still in develop):
email@example.com:~/simutrans$ sudo service simuserver status
[info] Simuserver: pak64-2... Not running.
[info] Simuserver: pak64.japan-1... Not running.
Possible states: No game data (place initial map, please), Ready to begin, Game stopped, Running.
Possible actions: start (makes sure server is running + starts cron watchdog to re-run it on crash), stop (stops server and watchdog), restart (stop+start), status (state+status info for each server). Watchdog also looks at savegame changes and makes backups every 2 minutes; it will keep backups in cascade manner: all 2min backups within a hour, all 20min backups within a day, all 2hour backups within a week and so on. I don't know exactly if it's safe to just copy savegame while game is running, so i'll have to find it out before doing such stuff.
When it'll be done, i gonna share that init.d script for people who will want to run it, too. Idk, gonna take some time.
Again, with paying more attention properties like pause_server_no_clients, which I used to set to "0". Server up ETA is 1-2 weeks, I surely need to test it first for savegame backup-ing stuff to not allow lose game data like I did few days ago.