Permissions Problems Using sudo to Run Server

[Llewen]

I'm having permissions problems with my TS server. I created a "teamspeak" user, then changed the ownership on all the ts folder recursively to that usr, "chown -R teamspeak:teamspeak tss*". When I ran the start script, "sudo -u teamspeak ./teamspeak2-server_startscript start" I got a permission denied error, the script couldn't create the ini file.

So I ran the script as root, and the server started no problem, and I set up the server. I then shut down the server, and made sure that all the files had the right owner, and changed the permissions recursively to 640, and for the script and executable to 755. Now when I try to start the server using "sudo -u teamspeak ./teamspeak2-server_startscript start" I get another permission denied error:

sudo: unable to execute ./teamspeak2-server_startscript: Permission denied

I am still able to start the server as root, but as I said, I don't want to do this. I want to run the server as the "teamspeak" user. I recently reinstalled my operating system after swapping some hard drives around, and I had the TS server running through sudo as the teamspeak user before with no problem. Any ideas on what could be going on?

The teamspeak user was created with the home directory of the root TS directory, the shell is "/bin/false", and I disabled the password and login for the user. I'm also having some strange permissions problems with logcheck and some logs and I'm wondering if the two problems could be related? The partition is mounted using the "nodev" flag.

I'm using Debian Etch, and I elected to install the basic system without any packages for specific configurations. I'm wondering if I am missing some necessary package that could be screwing around with permissions? When I installed previously I installed the webserver configuration.

What makes this even odder is I am running Half-Life and Source servers on the same box, using the same permissions configuration, with no problems whatsoever (ie. a user for the game servers and using sudo to run the servers, with fairly strict permissions). I also tried in exasperation setting the permissions recursively to 777, and had the same problem.

Any suggestions would be gratefully received.

[Llewen]

Finally got it. Read the noobs' guide. Created a user I could log in with. Deleted the files, logged in as that user, reinstalled the server, started it, and everything works. I can now use sudo to start the server. Guess my mistake was not realizing I was a noob...