Linux and Windows TS servers are bad

[Kaleva]

Linux server has no usable SystemV script to run as service (it should be placed into /etc/init.d/, and has start/stop/reload parameters, change UID on startup). I wrote this script, and may attach it here. (But it's copyrighted by me under BSD License)
Also Linux TS should be in RPM and DPKG packages, or have any another usable installer which should create user for running the TS daemon.

Windows TS server is VERY VERY BAD, because it's running in user's tray. This way is not usable in practical situations.
It should be running as Windows_NT service under LOCAL SERVICE or another unprivileged account. Service should be registered by the installer.

PS. Is any bugtraq for teamspeak????

[Reedy Boy]

All bug reporting is via this forum


There is an optional service binary for windows

http://www.goteamspeak.com/index.php...ownloads&id=6a


Some people prefer to run it under the local user, as they dont need to use it in a service state, and is therefore easier for them to start and stop it via that method - ie an icon in the start menu

A simple solution

If you have such a problem with the way that the software is coded - Don't use it

[Kaleva]

All bug reporting is via this forum
There is an optional service binary for windows

Thank you!

A simple solution
If you have such a problem with the way that the software is coded - Don't use it

It's not my choise to use TS, i'm system administrator.
If any open-source or just better analog of TS will be avaliable, I'll try to migrate my squad to it.

[Peter]

Linux server has no usable SystemV script to run as service (it should be placed into /etc/init.d/, and has start/stop/reload parameters, change UID on startup)

Hey, I intentionally didn't write such a script, because in the Linux world it's almost like each distro has it's own way of doing things (e.g. Gentoo which I use has its own unique init scripts).
So what I did was to write a script that could easily adapted for distro x y or z, when needed.

Also Linux TS should be in RPM and DPKG packages, or have any another usable installer which should create user for running the TS daemon.

This is the same story as above, there are many distributions, they use different package-formats, different locations as where to put the files etc. So what we did was to leave all files in one folder (which works for every distro), and let the distro users create their own packages (for gentoo there has been a .ebuild since ages, the client ebuild was helped by me even, for debian somebody was making a server package and mailed us for confirmation that what he was doing was ok with our license just a few weeks ago, rpms for the server have been posted to this forum, don't know if there are any up-to-date ones around...)

[Kaleva]

So what I did was to write a script that could easily adapted for distro x y or z, when needed.

Thank you for answer.
About your script -- some problem with it, because it thinks that TS binary is in running directory, also UID should be changed before. So I have written wrapper to it.
Can self-build TS packages produce problems with TS License?
If I build my own TS package and make it avaliable from the internet?