[llamabeast]

Wow, that was fast Ich.

For some reason dom3 doesn't give me any of that stuff back normally, and I couldn't work out where the temp directory was (although I use linux a lot there's a lot of things I don't know about it). Anyway, shortly after posting I remembered the debug switches, so I did dom3 -ddddd, which told me the location of the temp directory. Exactly why it was having a problem I don't know, but having deleted all the /tmp/dominions3_***** folders it's working again. Hurrah!

Sorry for solving it myself so quickly after posting - I'd actually already been stuck on it for quite a while. Anyway, hopefully this thread will be useful if anyone else has the same problem.

PS Actually, I can perhaps guess why it was having a problem. I think that the name of the temp folder is a random number using the system clock as a seed, but only to the nearest second (as it's the same if you run it multiple times in quick succession). If it uses the time but not the date for the seed, then running it at the same second on a following day would use the same folder name again. Since it doesn't delete the folders its created, this would cause a clash. Being as my server runs dominions at scheduled times, I guess it was hitting this problem.

What I'm going to do is make a 2-line script along the lines of

dom3 --someswitches
rm -r /tmp/dominions3_*

so it cleans up after itself. Windows users could do a similar thing with a .bat file.