small shell script for Linux users

[Crashzor]

For you how don't understand it put it in a file .sh
chmod 777 the file.
Type ./the file name server ip.
it will auto record a demo name of the demo will be
you're nickname ( or what ever you put in the script )_the time stamp
Its shot its simple and is handy for ladder matches

#change the nickname
nickname="change me";
#do noting here
date=$(date +"%Y%m%d%H%M");
./nexuiz-linux-686-sdl -sndstereo +record $nickname_$date +connect $1

don't know if it already hase been made or posted here

[esteel]

Would you have read all the PMs i wrote to you, you would have noticed this link: http://www.forums.alientrap.local/viewtopic.php?p=92#92
Oh and telling people to chmod 0777 a file is just bad.. 0755 would be more like it.. at least for those people that keep an eye on security!

[Crashzor]

o you're right about the chmod and i just notice the pm.
sorry litler error you can remove this thread

[esteel]

Nah.. maybe that way people find out about autorecord easier

[KadaverJack]

btw: Nexuiz 1.6 will have automatic demo recording as engine feature (the cvars are cl_autodemo and cl_autodemo_nameformat)

[esteel]

Guess i have to follow the DP cvs more closely.. does this also mean in-game record-starting does work?? But autorecording allone is great!

[KadaverJack]

does this also mean in-game record-starting does work??

No. But the enigne autorecording has the advantage, that you can switch servers and it will start a new demo automagically.

[esteel]

Yeah thats true. Hmm guess i'll change my record script to set the cl_autodemo variable to 1 when 1.6 is out because there is no need to record really every game..

[KadaverJack]

Yeah thats true. Hmm guess i'll change my record script to set the cl_autodemo variable to 1 when 1.6 is out because there is no need to record really every game..

I would prefer an "Autorecord On/Off" switch in the menu instead of a shell script. A good place for it would be in the join menu, next to the refresh button imho.

[divVerent]

For you how don't understand it put it in a file .sh
chmod 777 the file.

I don't want to be a nitpick, but: don't even get used to chmodding files 777.

If you own the file, all that matters is that you can do everything with it - that is, 700 suffices. Useful chmod values are:

• 600 - you can read/write, nobody else can do anything
• 640 - you can read/write, your group can read
• 644 - you can read/write, everyone can read
• 660 - you and your group can read/write, nobody else can do anything
• 664 - you and your group can read/write, everyone can read
• 666 - everyone can read and write

Additionally, shell scripts and programs need to be marked as executable so that the OS knows it is a script/program. This is basically done by replacing all fours by fives and all sixes by sevens. The access rights in the list would then be: 700, 750, 755, 770, 775, 777.

Usually, you don't want to give more access rights than 644 for regular files and 755 for directories and programs/scripts. These rights mean "everyone can read/execute/enter, nobody except you can write".

Of course, all this does not matter if you are the only one who uses the computer - but if you use "wrong" chmod values in a multi-user system like at university or on hoster where you can run a dedicated server, you can get severely screwed, that is, "owned" by others who access the same computer.