Minilogin, Ports, Shorewall Info

[Angelox]

Some of my zones are not loading fast enough, which results in client crash when booting up the dynamic zones.
An error example;

Zone bootup timer expired, bootup failed or too slow.

When zoning, usually what happens is, the new zone auto-boots and thinks it has the player in the zone. But in reality, the client is crashed for the server taking too long to boot up.
I'm thinking the reason for this is because my machine is too slow on loading all the new data I have added to the given zone (i'm runing a PIII with 1.5gig ram).
This started when I did some changes to loots, and have just about every mob in the game droping something: on big zones like the LoY zones, changes like this are massive and I imagine require extra loading time.

anyways here's a new start up I devised which adds static boot up too the slow loaders;

#!/bin/sh

wine MiniLogin.exe > logs/MiniLogin.log &
P=`pwd` 
export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:$P"
#make sure we have a place to log
mkdir -p logs 2>&1 > /dev/null 

#boot up world
if [ ! -e .lock-world ] ; then 
	    touch .lock-world 
	    ./world & 
	    # wait for shared memory to load
	    sleep 20 
fi 
#start up the official launcher
if [ ! -e .lock-launcher ]; then
	    touch .lock-launcher
	    ./eqlaunch zones &
	    sleep 80
fi
	    ./zone gunthak 7006 &
	    sleep 5
	    ./zone dulak 7007 &
	    sleep 5
	    ./zone torgiran 7008 &
	    sleep 5
	    ./zone nadox 7009 &
	    sleep 5
	    ./zone nurga 7010 &

I know it's crude compared to what you guys posted - so you "pretty" it up

And here's a working stop (I kept having port problems with mini-login and the wine-server);

#!/bin/sh 

killall wine MiniLogin.exe world eqlaunch zone wineserver wine-preloader
sleep 3

if ps ax|grep -e 'w[o]rld' -e 'z[o]ne' -e 'eq[l]aunch' >/dev/null; then
	            killall -9 world eqlaunch zone
	            sleep 2
fi

./cleanipc 
rm -f .lock-zones .lock-world .lock-login .lock-launcher

[John Adams]

FYI Angelox, my Core 4 machine is currently P4 1.5GHz, 512m RAM, and a 40GB Quantum Fireball (I think that's 7200 rpm). I haven't had a zone load problem yet, but I am also not running any x-windows at all. Not sure how this stacks up against your machine.

But of course, now I have a new excuse to visit newegg.com, don't I?

[eq4me]

Just a shot in the dark:
If you are using IDE disks maybe DMA isnt turned on.

To check the rough speed of your disk(in this example /dev/hda) install the package hdparm and do

hdparm -Tt /dev/hda

The "buffered disk reads" should be well over 20 MB/s with any halfway modern harddrives.

If they arent check if DMA is turned on.

hdparm /dev/hda

"using_dma" should be 1. If not you have an huge disk I/O performance penalty.

More in this guide, its slightly gentoo specific but quite good
http://www.gentoo-wiki.com/HOWTO_Use...ce_performance

[Angelox]

Originally Posted by John Adams

FYI Angelox, my Core 4 machine is currently P4 1.5GHz, 512m RAM, and a 40GB Quantum Fireball (I think that's 7200 rpm). I haven't had a zone load problem yet, but I am also not running any x-windows at all. Not sure how this stacks up against your machine.

But of course, now I have a new excuse to visit newegg.com, don't I?

Your pc is much more up to date, mine is way behind (P3 875MhZ) - the problem is there,x-windows or not. my 1.5 gig of ram will not make it run any faster, just buffer things and help out with the static zones.
That's just what I use for a server, I do have my personal machine which is P4 2.5 GhZ, but I don't want to turn it into any kind of a server.
I "almost" have a P4 Celeron put together - All I need is a motherboard. I had bought one on sale, one of those "as you see" no return" deals, but turns out it's for Pentium 4 CPU only, and not Celeron. So now I have a nice, shiny new MB to look at. When I get that one running , I'll move everything to there.

[Angelox]

Actually, the static zones are pretty nice, gives you a more realistic view of the game (as in Live); mobs that get killed re-spawn again within their time limit , even if the zone is empty. Also, if a named mob is up, you can get killed, then come back try kill him again, but if you're dynamic, the zone re-boots when you die, and it's all over.

[fathernitwit]

John, few comments about your script:
1) I wrote the original
2) I would move the LNAME code up to the top of the script, its really a configuration, not a start thing...
3) the LNAME test condition needs to be change to $2 instead of $1 since you added start/stop to the cmdline
4) when you stop minilogin, im pretty sure you need to be killing wine, not MiniLogin.exe. But that might upset things if they are using something else in wine... might wanna grep for the pid or something.

Angelox: booting zones directly really isnt advised... especially on linux... the launcher is designed to automatically inject delay into zone booting to prevent your problems.

[John Adams]

FNW, thanks. I will make the changes, test them, and WIKI this script.

[Angelox]

Originally Posted by John Adams

FNW, thanks. I will make the changes, test them, and WIKI this script.

At the end, you do have to kill the whole wine server, so it gives up the port minilogin uses- I don't use wine of that machione for anything else so it's not improtant for me to keep it running;
My latest stop-script;

#!/bin/sh 

killall wine MiniLogin.exe world eqlaunch zone wineserver wine-preloader
sleep 3

if ps ax|grep -e 'w[o]rld' -e 'z[o]ne' -e 'eq[l]aunch' >/dev/null; then
	            killall -9 world eqlaunch zone
	            sleep 2
fi

./cleanipc 
rm -f .lock-zones .lock-world .lock-login .lock-launcher 

sleep 3
killall wine-preloader
sleep 3
killall wine-preloader
sleep 3
killall wine-preloader

The third "killall wine-preloader" returns the error that the job is done.