Linux Server

[Shotglass]

Ok, I couldnt find anything on the forums about this, so I will ask. I guess I am an idiot, but I have only been using Linux officially for about 3 days now, I have TS server files downloaded, but cant seem to get it to do anything. I have an installer folder, but when I click on the Executable file, nothing. I am running under KDE mode, not sure if that makes a difference. Can anyone help me?

[FloorPie]

Welcome to linux.

If you've extracted the files from the 'tar' correctly, you'll end up with files called:
  server_linux
  tss.minimal_startscript
(and more).

In this directory, I start mine by the command:
./tss.minimal_startscript start
or the full path: (example)
/home/billyj/tss2/tss.minimal_startscript start

Initially, I had to extract the tar (ts2_server_rc1.tar.tar) with the command:
tar jxvf ts2_server_rc1.tar.tar

This created the 'tss2' directory in the folder the .tar was in.

Hope this helps.

[Shotglass]

ok it says it started, but how do I configure it?

[FloorPie]

Edit the server.ini, then restart the server.
./tss.minimal_startscript restart

[[HJ]-Petz]

Since this is a thread for linux newbies ill post here.

I have the server running fine using the minimal script and I can configure it.

However I need help to make TS2 into a linux service that loads at boot time. Can someone who knows give me a quick how to.

Specs
Slackware 8.1(stock iso's no changes)
AMD-K6 166mhz
24mg ram
and a small arse hard disk (so ive cut down on alot of option packages including KDE,GNOME, X :))

Thanx

P.S. Also whats the best place to store the server files. atm ive got them at /root/ts/ts2 which i know probably isnt the best place to have them stored.

[ScOp3]

Okay i try to help :)

But i'm not the linux crack in fact. The Problem with Linux is, every Distribution handels stuff a bit different and i haven't seen slackware in action so far.

I try to explain what i have understood so far.

Linux uses several Running States e.g. u can define State 1 Load Programm A&B, State 2 Load A&B&C to make it a bit abstract. In 99% of the case we talk about Runlevel 2 or 3, where 2 is mostly multiuser Linux system and 3 multiuser Linuxsystem with X Desktop/Server.

In you're case first of all find out which "runlevel" your system is currently. An easy way should be typing "runlevel" on the shell prompt. The Answer should look like "N 2" or "N 3", at least it does on my debian system.

After u have found out the runlevel u know where to edit. The Configuration for each runlevel is being held in directory's which are created according to the run level.

e.g. in my distribution the config dir for rl 2 is /etc/rc2.d and for rl 3 it's /etc/rc3.d. In you're case it should be very similiar.
If u have a look into the directory u see a lot of so called soft symbolic linksc which are comparable to a shortcut in Windows but being much more sophisticated to use.

The symlinks u see, all have a name starting with a letter and a number. e.g "S20ssh -> ../init.d/ssh" or "K10ssh -> ../init.d/ssh2"
The Letter S means start and the lette K means Kill which is similiar to stop :) The numbers are like priority's. First ist starts 10 then 20 then 30 etc etc. The Kill process is top down, meaning it kills 30 then 20 then 10 etc etc.

What u actually have to do, to get you're script being called every time the system is booted. Is to make a symlink to the script which could looke like this

"S20tsserver -> ../init.d/minimal_startscript"
"K30tsserver -> ../init.d/minimal_startscript"

The command u have to use for creating symlinks is "ln". If you're script minimal script would reside in /usr/local/tss2/minimal_script, the syntax for creating a ln inside rc2.d would looke e.g. like this.

"ln -s /usr/loca/tss/minimal_script S20tssserver" &
"ln -s /usr/loca/tss/minimal_script K30tssserver"

Double check that u always use the option -s, otherwise you created a hardlink. Which means that if you delete the link, the original file get's deleted as well !

If everything worked out well, the server should be started at boottime. But of course u have to experiment and read a bit to get working the first time.

This is as good as i can explain so far, there maybe other or even easier methods of doing this but then u have to wait for a real linux crack.

Greetings

ScOp3

[[HJ]-Petz]

Thanx heaps for your help and time

Ill give all that a go and see what I can get going soon (im out of time have university exams comming up :().

So far before you posted

I have already worked out my default runlevel is 3 and i think the related file for that runlevel as discovered in "/etc/inittab" was rcM.d But don't think i found any symlinks. Just a script file (ill look again though I might have missed it). Is making the sym link to the TS_minimal_script all I have to do(the server starts when the machine is booted and stops when shutdown)?

Just another few questions though.
1. You didnt mention where is the best place for the server files. Recommendation? Also ive seen posts about getting the server to run under a user account instead of the root user. Should I do this? If so how? If I create the sym link as you stated whos account is the server running under(I presume root)?
2. When I get it fully setup. What will i need to do to start and stop the server(cause from using the windows version this is the only way to update the database file ie. Save registered users details and such)?

[ScOp3]

Originally posted by [HJ]-Petz
1. You didnt mention where is the best place for the server files. Recommendation? Also ive seen posts about getting the server to run under a user account instead of the root user. Should I do this? If so how? If I create the sym link as you stated whos account is the server running under(I presume root)?


What you are looking for was really nice explained in a debian starting script thread. Fortunatly i use debian which made me able to reduce the number of tweaks drastically. But i suggest u check out following thread.

http://www.teamspeak.org/forums/showthread.php?s=&threadid=998

This is information is what i used to create the tss2 user and to sort the binary and the log and stuff in to separate directory's.



2. When I get it fully setup. What will i need to do to start and stop the server(cause from using the windows version this is the only way to update the database file ie. Save registered users details and such)?

What you do right now i guess is, is calling the script with <srciptpath>/minimal_startscript start or stop.
If you do it as explained above with the S and K style. The system issues the start and stop command according to it's systemstate. Booting issues start and rebooting issues stop e.g.
So if u have created those symlinks to the startscript it should work automagically :)
Again i advise to check the debian script mentioned in the thread above. This might help you to understand more on how it works.

This is what i have used to get around so far.

ScOp3