From: "Ken Kirchner" <[EMAIL PROTECTED]>
> >
> > Woops, my bad. In my haste I missed out a critical step in the upgrade
and
> > ended up running half 3109 half 3110 :)
> >
> > Working fine now.
> >
> > -Simon
>
> How in the hell did you manage that? My tar shows no mercy.
>
I use a system of symlinks to keep differing versions of each of the dlls
and suchlike, so that I can rollback if an upgrade goes wrong (mostly useful
with the beta servers and stuff like meta/admin mod, hlguard etc.), and so
that the multiple servers on each machine can be updated without closing
down all the servers before doing the upgrade, minimising downtime (as the
servers can be running different versions simultaneously).
Like this:
halflife/
hlds -> hlds.3.1.1.0
hlds.3.1.0.9
hlds.3.1.0.9b
hlds.3.1.0.9c
hlds.3.1.1.0
engine_i386.so -> engine_i386.so.3.1.1.0
engine_i386.so.3.1.0.9
engine_i386.so.3.1.0.9b
engine_i386.so.3.1.0.9c
engine_i386.so.3.1.1.0
halflife/cstrike/dlls/
cs_i386.so -> cs_i386.so.1.5
cs_i386.so.1.4
cs_i386.so.1.5
metamod_i386.so -> metamod_i386.so.1.12.2
metamod_i386.so.1.12.1
metamod_i386.so.1.12.2
And so forth. This is actually standard practice for libraries on linux
systems (just take a peek in /usr/lib and you'll get the idea). I've
occasionally thought of suggesting this practice be adopted by app/mod
developers, but figured it might just confuse people. ;)
The mistake I made here was that I updated the cs_i386.so symlink but forgot
about hlds and engine_i386.so. So I was running v1.5 with HL 3109 (oops).
-Simon
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux
