so here's my scenario.

I've got a dedicated server running slackware 10.2 that will be serving day of defeat source.

there are 3 users with shell access and i would like to use screen to allow each of them to retrieve the console at various times.

I figured making a script that would launch the server (using screen) as a 4th user using sudo (i know the other 2 users with shell access personally) and another script using that 4th user to retrieve the server would help fix this (script follows

to launch the server:

echo "Starting DOD:Source Server"
sleep 1
sudo -u source screen -A -m -d -S dod ./srcds_run -console -game dod
exit

to retrieve it:

echo "Retrieving Server"
sleep 1
sudo -u source screen -x dod
exit


So my current problem is this error:

You are not the owner of /home/jetpig/.screen.

the server and scripts are located in /home/source/srcds_1/
i'm launching as the user jetpig and am executing the scripts while in the srcds_1 folder.


Any help will be greatly appreciated.



thanks in advance!

The only thing I can think of is that you created /home/jetpig/.screen as root. Therefore, you are not the owner.

Check the ownership: ls -l /home/jetpig/.screen. If jetpig isn't the owner, you will have to su, or sudo, to root, then use the chown command to change ownership.

that returns:

"total 0"

what's odd is that screen is giving that error when there's nothing in that folder and the user source is trying to run it.

It sounds like it's finding the file (since it doesn't say "No such file or directory"), but since it's a hidden file it's not displaying it. Try again, adding the -a switch i.e. 'ls -al /home/jetpig/.screen'.

that returns:

total 1
drwxrwxrwx 2 source users 48 2003-07-05 19:10 ./
drwxrwxrwx 4 jetpig users 160 2003-07-05 15:03 ./

(that's something else.... time won't stay set across reboots)

I found your problem (probably), while playing around with sudo trying to make a script that returns the user it's running under, and thought it was strange that the sudo 'lasted' until the end of the line, whereas similar things like su -c didn't.

Of course, I was wrong (I've never used sudo, personally) and it turns out that sudo acts for one character. Try wrapping your commands in quote marks, like so:and(And I had a really fancy script ready too, based around the fact that whoami "doesn't work under sudo", which of course it does if wrapped in quotes properly )

now this is odd.... "sudo: screen -A -m -d -S dod ./srcds_run -game dod ... (trails off with a ton of other launch options) ... +autoupdate: command not found"

i tried explicitly telling it wghere srcds_run was also. it seems that it doesn't like the screen command though.... i tried running it straight from the source user and it worked fine

It's the 'screen' command that it's trying to run, all the other words are just arguments to that command. I must admit, I'm not really sure where the problem lies here, but you could trywhile logged in as both jetpig and source to check that they both have the executable in their path - and a final paranoid just to make sure that sudo isn't messing it up. If they all locate the command fine... then you could try explicitly adding the full path to the screen commands in your script.

It's got to be something fairly simple, with an error like "command not found"...

i get /usr/bin/screen for jetpig and i get sudo: which screen: command not found. i took out the quotes and it works fine... *sigh* like you said, something simple.


ok well the launch script works. now i can't retrieve it. both as user jetpig and source i'm told that there is no screen to be attaced matching dod.

if i try sudo -u source screen -x dod i get Cannot open your terminal "/dev/pts0/0' - please check.

is it possible it thinks i'm not a vt100 terminal?

*bump*