RC1 vs RC2 question ?

[Cometcom1]

From what I have read in the threads, there is quite a difference in the two version. But what I am particularly interested in knowing a little bit more about is the database of channels and passwords at the time of terminating the process.

From my experience, the RC1 server does some database operation at the time it calls exit. And for some reason that rewrites the database entirely.

In case the process is somehow terminated too quickly, the database gets out of bounds and the next time the server starts it's all mumbo jumbo or a few channels could be lost.

Will the new database in RC2 fix this problem ?

Assuming the database update is done through a separate thread, and assuming this thread is not monitored for completeness before the final exit to system routine is called, this might still happen after the RC2 release.

I'd like comments from the Dev Team, or anyone knowing how this is done.

Info:
Windows 2000 Server, Fully patched
P3 - 500
512 MB Ram
Lots of disk space (8 disks in total RAID)

[R. Ludwig]

<From my experience, the RC1 server does some database <operation at the time it calls exit. And for some reason that <rewrites the database entirely.
yes thats true, its a btree database and its writes itself completly down at exit of application.

<In case the process is somehow terminated too quickly, the <database gets out of bounds and the next time the server <starts it's all mumbo jumbo or a few channels could be lost.
i got only once such a mumbo jumbo database, and that was just because someone killed the complete process while it was safing the db (450 servers).

mostly you loose channel informations because teamspeak server only writes down infos at termination time. if server gott killed before it was able to write anything down the infos are gone.

<Will the new database in RC2 fix this problem ?
i dont know yet if rc2 will contain the new database core already.
but we will use something like sqlite for normal servers. if someone is intrested he can also use mysql, oracle or postgres.

so with the release of this new database core, all problems will be fixed and this release will come with rc2 or directly after that.

hope the infos are ok for you ...

[Cometcom1]

Just the information I have been seeking.

Somehow I have had this problem since I installed RC1 - It does happen both when I kill the process prematurely (which is expected really), but also if I stop the process normally. It's been quite annoying.

Glad I got this great reply, I will be looking forward to RC2 and the end of all my trouble.