the linux build of srcds will generate this error right out of the box.
to "see" the error message from the console, start your srcds_run
through a screen process (be sure to use -autoupdate in your start
vars), add some bots (or players, if you have them) to generate cpu/mem
usage, then from the server console, QUIT.
The -autoupdate var will allow the process to kill itself, and restart
in X seconds without killing your screen session, or the console itself,
and it will also generate any shutdown/rstart errors.
ex :
screen -dmS CSS nice -n -15 ./srcds_run -autoupdate -game cstrike
+ipx.x.x.x +port XXXXX +exec server.cfg +whatever else
then
screen -r CSS
Alfred Reynolds wrote:
What mod? And does an empty server exhibit the same problem (or put
differently, how do I reproduce the problem here at work).
- Alfred
----Original Message----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED] Sent: Friday, May 27, 2005 8:08 AM To:
[email protected] Subject: [hlds_linux] SRCDS Memory
Leak
I think I've seen some conversation on this in the list already, but
I'm wondering if others are still seeing
the memory leak in srcds. I just configured mrtg to
monitor my memory utilization and I can see the leak now.
Srcds is the only application I use on the box and I'm seeing the
following:
- After 12 hours, memory utilization starts to creep up.
- By 16.5 hours it has doubled.
- By 22 hours it has tripled.
I'm obviously adding a server reboot into cron as a short term fix.
Fedora Core 3 - Fully patched
1 Gig Mem
3.0GHz Processor
Am I nuts, or is this legit? If it's legit Alfred, any
leads on the cause of this?
Snewo
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux
