----- Original Message -----
From: "Michael Peligro" <[EMAIL PROTECTED]>
To: "PLUG Philippine Linux Users Group" <[EMAIL PROTECTED]>
Sent: Sunday, June 16, 2002 7:08 AM
Subject: [plug] Linux Counter-Strike Server 1.3


> I'm really impressed with the performance of my LAN server. CS1.3 paired
with HLDS Ping Booster, the
> clients were fast and lag was
> reduced.

actually it was the ping booster who helped cs 1.3 to minimize the lag

> My latency fell to an average of 20-25. I'm running this server on
console, runlevel 3. At first, I was
> running it on X (with
> Blackbox as my window manager), but I fear that I couldn't maximize its
speed while on X.

thats good.... its a bad thing running an application that doesnt need X
specially on a dedicated server.

> and will go for 1.4 (1.5,
> actually) after upgrading our hub to a switching hub later next month
(nakaka-inggit talaga ang switching hub.

you should but i recommend its a must because majority of multiplayers games
are using udp protocol and udp protocol is unreliable protocol... once the
udp packet is loss due to collision under the hub environment, it will
create a lag due to resending and recalculating at the client side.

> Padalhan sana kami ni
> Santa Claus. Honest counter-strikers naman kami, ah!)

eh hindi naman mahilig si santa clause sa santa strike este counter-strike
eh :->

>
> Does anybody here have similar experiences in administering a
Counter-Strike/Half-life/Team Fortress/Death
> Match Server on Linux?

cs over linux is good but cs over freebsd is much better.

>
> I have several questions for your consideration. These concerns my Counter
Strike server and Linux set-up
> as well:
>
> 1. Does memory leaks occur when running X? I notice that my server gets
noticeably slow at least once
> every 5 hours. I read
> somewhere from the Internet that X is poor in cleaning up the memory that
it uses. Is this true? Or is it
> slocate updating its index once
> in a while? Is it right to reboot the server once every 5 hours to refresh
the memory usage/leaks?

for a short term solution yes but for a long term solution... upgrade or
apply any patch.

>
> 2. I've pruned all services to the bare essentials. My file-system is
ReiserFs. Should I use ext3 instead? Which
> is faster based on your
> experience? ext3, JFS, or ReiserFs? Kung konting speed differences lang
naman among the three, I might as
> well stick with ReiserFs.

it just a matter of getting a filesystem benchmark tools to know their
differences... when benchmarking, just be aware of disk buffering and
location of a filesystem on the disk platter because outer tracks are faster
than the inner tracks.

>
> 3. I've been using KDE System Guard to monitor my server's performance and
throughput. However, soon
> after exiting the program,
> my server would slow down a bit.

????

> I know that KDE is a memory hog. Is it really advisable to avoid using KDE
> GUI clients in Blackbox?

if an application doesnt need kde dont use it

>
> 4. I am fairly inexperienced with regards to the setup of
Counter-Strike/Half-Life Windows clients. Can
> anybody send me their
> config.cfg, autoexec.cfg, server.cfg, listenserver.cfg? What values (such
as sv_maxrate, sv_maxupdaterate,
> cl_updaterate,
> cl_cmdrate, rate, etc..) do you recommend for 10mbps networks?

why not? 10mbps is too way fast compare to 56kbps dial-up counter strike
clients.... if you are talking about 10mbps for lan clients and dont want to
hog your 10mbps bandwidth, control and dictate your cs server how fast the
cs clients transmit and rate limit their data to your server... i think its
on the sv_maxrate parameter..

>
> 5. Ano'ng peborit ninyong server OS? Red Hat? Debian? Slackware? Mandrake
gamit ko kase newbie pa ako.

its up to you to decide where you find comfortable most...... kung saan ka
maligaya.. suportahan gid kita! :->

fooler.

_
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]

To subscribe to the Linux Newbies' List: send "subscribe" in the body to 
[EMAIL PROTECTED]

Reply via email to