[bf1942] chown on start?

[Bill Cuffley]

Well, my situation is similar, I need to have the perms of the config
files set as 660 (don't ask), since when the server dies, it changes
everything back to 600 or 700. Anyways, I added these lines to my
startup script:

stop_game() {
        echo "Signal Caught, killing game"
        killall bf1942_lnxded
        #re-setting permissions
        find . -type f -exec chmod o-rwx {} \; -exec chmod g-rwx {} \;
        find $CFG -exec chmod g+rw {} \;
        exit 0
}
trap stop_game 2

I usually kill the server with a good ol' ctrl-c (SIGINT/2), so the
killall command is useless, but I leave it there just in case.  The trap
command will make it so the stop_game function is called when the script
receives a SIGINT (signal #2 = Ctrl-C)

Enjoy

Bill

-----Original Message-----
From: Casey Zacek [mailto:bfb-bf at bogleg.org] 
Sent: Thursday, June 26, 2003 11:42 AM
To: bf1942 at icculus.org
Subject: Re: [bf1942] chown on start?

Christian Lahme wrote (at Thu, Jun 26, 2003 at 05:27:22PM +0200):
> 
> Hello Andreas,
> 
> Is bf1942_lnxded doing a chown every start? Is it possible to set this
> by ServerSettings.con. Our System has to have different owners for the
> configfiles. The starting user is in a group with the file-owner, but
> they aren?t the same.
> 
> Is there any possibilty to get this in next ob?

Only root can chown.  I don't run bf1942 as root, so mine certainly
isn't chowning anything.

-- 
-- Casey Zacek (Zippo)                  Beer for Breakfast servers
   66.111.111.66:27015 (CS multi-map)     <http://bfb.bogleg.org/>
   66.111.111.66:27016 (CS inferno/dust2/aztec/militia) Dallas, TX
   66.111.111.66:14567 (BF1942)