|
|
[ Installation and setup ] [ Known Problems and Bugs ] [ eQSO x home ]
eQSO X Server Installation
The first time you launch the daemon you need to input your settings (this is pretty much the same as with the Windows version).
eQSOx will detect the lack of an existing .conf file and prompt you through creating one as per the below screenshot.
The options in square brackets "[ ]" show the default settings. Leaving a blank and just hitting return will use the default setting, although I would recommend changing the password...
To stop the daemon, use the "-STOP" command line parameter as per the following screenshot.
Issuing "Killall -9 eqsoxd" will also do the trick.
If you wish to restart the server, you should wait at least 2 seconds to allow all threads to terminate themselves. Not doing so is likely to result in an error when you restart.
Once you've launched the server for the first time, a .conf file is created with your settings to save you putting them in each time. Next time you launch, the daemon will show you it's current settings and port binding.
The "active rooms" list is maintained in the text file "xroomlist.txt" which should be left in the same directory as the server daemon. The contents of that file should look something like this:-
# Add 'fixed' Rooms here
# The name of each room must be less than 10 characters
#
# Put each room on it's own line
#
446ENGLISH
446DUTCH
446FRENCH
If you wish to create additional standard rooms, edit this file in a text editor and then save it.
Doing a PS AX at this point, with no clients connected, should look something like this.
You'll note a total of 6 threads running for the process. These control the I/O for eQSOx:-
Every time a new client connects, two new threads are spawned, one for outbound message queuing and the other for inbound for that client.
So if you have 50 clients connected, you'll see a total of 106 threads. Don't be scared by it, Linux uses the POSIX thread model which is extremely efficient. Run "top" and have a look at CPU load when the server is active and you'll see what I mean.
Most Linux kernals can handle 256 threads per process, which makes for a theoretical maximum of 125 users. If you need more than that, you'll need to recompile your kernal and change the max_threads_per_process variable to 512, or higher.
Each connected client has inbound and outbound buffers assigned to it of 8192k each so total memory useage should be about 16k per connected client plus the memory useage of the server itself.
This is a little tool that you can run at the command line and see what's going on. It's very BETA, in fact, you might even be the first person to test it apart from me. If it doesn't work on your build of Linux, it's probably my Quick Sort routine trying to put everything into order. I'll get around to tidying that up - some flavours of Linux don't like it. Works fine on Mandrake, Debian and FreeBSD. Should be ok on any Intel Unix also (although I haven't tried it).
Launching it for the first time will again walk you through a few prompts and then you should see something like this.
The traffic reports are total traffic in either direction, and not bandwidth which is something I want to add later.
I do have command line tools for mute, kick and ban although I'm not releasing those just at the moment (need a bit of tweaking).
The standard Windows admin client can be used with eQSOx, although when you connect you'll notice that the clients are not displayed in room order. This is something that I want to change on the Admin client and I'll get around to it at some point - I'd rather put sort routines client-side rather than server-side as it's client work, and an unnecessary load on the server.
Any problems you can get me at eqsox@446user.co.uk. Please use that address for any queries or problems relating to eQSOx so that I can maintain all emails in one folder.
73
Dean