SIGINT and SIGKILL are not commands, they are methods of killing processes used by programmers.
Off the top of my head a SIGKILL can be done by using this command: kill -9 pid And a SIGINT is just a normal kill: kill pid Best to try and use the second one first as it will try to gracefully close the process. If that doesn't work try the first. pid is obviously the process id of the game server you are trying to get rid off. On Sun, Dec 13, 2009 at 6:38 AM, Saint K. <[email protected]> wrote: > I just had another forked server goin mental on me. I tried the SIGKILL and > SIGINT commands but they don't work (command not found). Where am I suppose > to execute these commands? > > Cheers, > > -----Original Message----- > From: [email protected] [mailto: > [email protected]] On Behalf Of Milton Ngan > Sent: Monday, November 30, 2009 12:39 AM > To: Half-Life dedicated Linux server mailing list > Subject: Re: [hlds_linux] Crashing L4D2 fork killing entire machine > > If you guys are running the servers with -debug (which doesn't currently do > anything useful in -fork mode) or crash dumps enabled you should send a > SIGABRT (-6) to the process to get it to dump a core file. It will also kill > the fork as well. SIGKILL should be used as a last resort if SIGINT > (standard kill) doesn't do anything. > > With regards to -debug and -fork, I have a Perl script that I run alongside > srcds_run to achieve desired behavior. I need to re-write this to be more > portable so that it can be shipped. > > -----Original Message----- > From: [email protected] [mailto: > [email protected]] On Behalf Of riemers > Sent: Saturday, November 28, 2009 11:49 AM > To: Half-Life dedicated Linux server mailing list > Subject: Re: [hlds_linux] Crashing L4D2 fork killing entire machine > > I've seen a process with 100% too, i've also seen a server which was full > for like 2 hours on the same map. > At that point i check it out, and it seemed the 4 survivor bots where > playing against the infected bots, over and over again. > > Somehow still pretty funny.. > > On Sat, 28 Nov 2009 20:13:44 +0100, Saint K. <[email protected]> > wrote: > > I have had this issue twice up till now, and it's rather disturbing. > > > > What happened is that a L4D2 fork gets in a crashing mode of some kind > > where it continuously puts 100% CPU load on a single core. I've seen > these > > sort of crashes perhaps around 10 times so far. 8 times I've spotted it > > soon enough to kill -9 <pid> the process, and 2 times I've been too late > > and it been in such a state for several hours before it will entirely > kill > > off the machine. The machine will only reply to icmp and nothing else > (ssh, > > http, ftp, gameservers etc). > > > > This worries me a bit, because I do not have any reason to assume > > something is broken on OS or hardware level. > > > > Regards, > > > > Saint K. > > > > _______________________________________________ > > 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 > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 9.0.709 / Virus Database: 270.14.87/2534 - Release Date: 11/29/09 > 20:31:00 > > _______________________________________________ > 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
