On Tue, Sep 14, 2010 at 01:46:35AM -0400, clad iron wrote:
After looking into this, i have question for everyone that is having this
same problem. ( windows and linux )
We run sourcemod, can anyone else having these problems verify they run
sourcemod also ?
I found this in our logs which is
Ok. Since the last MAJOR update (protocol 47 to protocol 48) (a year and a
half has passed since then), I'm constantly getting these kind of errors:
./hlds_run: line 321: 8644 Segmentation fault $HL_CMD
I've read 1/2 the internet to find a solution AND nothing!!!
Using: slackware 13.0, 32 bit,
are you sure this is not an hardware related problem?
(are you getting this everr everytime on the same occasion or is this
happening randomly like when you have bad RAMs?)
On Tue, Sep 14, 2010 at 6:48 PM, Anthony Stoyanov
bg.1nv1s1...@gmail.com wrote:
Ok. Since the last MAJOR update (protocol
No crashes here, fully loaded server with both meta and sm plugs.
On Tue, 14 Sep 2010 06:11:50 +, Harry Strongburg harry.h...@harry.lu
wrote:
On Tue, Sep 14, 2010 at 01:46:35AM -0400, clad iron wrote:
After looking into this, i have question for everyone that is having
this
same
Positive it's not hardware. I've got 6 different machines (all of them
running slackware), and on each one of them i get this error.
--
Message: 4
Date: Tue, 14 Sep 2010 19:55:03 +0200
From: Marco Padovan evolutioncr...@gmail.com
Subject: Re: [hlds_linux]
What is the most efficient way to block DoS attacks?
So far I used this pluginhttp://forums.alliedmods.net/showthread.php?t=95312.
Would it be better to block it with iptables instead? If yes, how?
___
To unsubscribe, edit your list preferences, or view
Perhaps something in Slackware then?
-ics
14.9.2010 22:28, Anthony Stoyanov kirjoitti:
Positive it's not hardware. I've got 6 different machines (all of them
running slackware), and on each one of them i get this error.
--
Message: 4
Date: Tue, 14 Sep 2010
I have the same problem, debian 64 its software related problem. My
hardware was tested one week under load, memtest, harddisk test.
Ok. Since the last MAJOR update (protocol 47 to protocol 48) (a year and a
half has passed since then), I'm constantly getting these kind of errors:
./hlds_run:
You can block the IPs via iptables, but your server still has to process the
packets which will still bog down the server. The best thing to do is talk
to your GSP and have them block the IPs before it reaches your server so it
bogs them down and not you.
What is the most efficient way to block
hey guys,
dystopia is out and we are running out of dedicated servers, would u
guys give us a hand?
./steam -command update -game dystopia
http://www.dystopia-game.com/
thanks! ;-)
-atomy
___
To unsubscribe, edit your list preferences, or view the
iptables -N logattacker
iptables -A INPUT -p udp -m udp --dport 27015 -m length --length 0:32
-j logattacker
iptables -A logattacker -j LOG --log-prefix SRCDS:ATTACK:
--log-ip-options -m limit --limit 2/sec
iptables -A logattacker -j DROP
Shamelessly stolen from:
11 matches
Mail list logo