kyle wrote:three questions that may be helpful
How did you compile it?
How did you start it?
What are the file permissions?
Good point, I should have stated those things first.
Code: Select all
bzr lp:armagetronad
cd armagetronad
./bootstrap.sh
./configure --prefix=/home/compguygene/trunk --enable-dedicated --enable-armathentication --enable-ruby
make
make install
These operations were done on an Ubuntu 14.04 VPS as a regular user. The only errors encountered were at the end of the make install, it failed on the creation of the uninstallation script.
I started the server using a script. But to ensure that the script was not the problem, I manually entered the following command to start the server, which other than lacking to start it in a screen, is the same as the script:
Code: Select all
/home/compguygene/bin/armagetronad-dedicated --vardir home/compguygene/servers/threetmft/var
As to the file permissions, I did ensure that I own the files with a
Code: Select all
chown -hR /home/compguygene compguygene
and in every other way the file permissions are normal.
Z-Man wrote:We no longer include configuration files from the var folder in 0.4. Players can partially control the contents of that folder. On 0.2.8, we still allow *.cfg files to be included from there for compatibility reasons and because none of the native player controllable files have that extension.
By this did you think that I was running a server from my client? I now realize that from my initial post that was very unclear. I am running a server on a VPS. I have seen the same, unrelated error on my server console and on a client build on my desktop PC.
So, are you saying that we me having started the server with the command
Code: Select all
/home/compguygene/bin/armagetronad-dedicated --vardir /home/compguygene/servers/threetmft/var
I still can't keep config files in the /home/compguygene/servers/threetmft/var directory? If not there, then where?