Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262646AbVCVLuH (ORCPT ); Tue, 22 Mar 2005 06:50:07 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262647AbVCVLuH (ORCPT ); Tue, 22 Mar 2005 06:50:07 -0500 Received: from linux01.gwdg.de ([134.76.13.21]:59832 "EHLO linux01.gwdg.de") by vger.kernel.org with ESMTP id S262646AbVCVLuC (ORCPT ); Tue, 22 Mar 2005 06:50:02 -0500 Date: Tue, 22 Mar 2005 12:49:58 +0100 (MET) From: Jan Engelhardt To: Hikaru1@verizon.net cc: linux-kernel@vger.kernel.org Subject: Re: forkbombing Linux distributions In-Reply-To: <20050322112628.GA18256@roll> Message-ID: References: <20050322112628.GA18256@roll> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 842 Lines: 27 > >This will prevent it from exceeding the procs limits, but it will *not* >completely stop it. What if the few procs that he may spawn also grab so much memory so your machine disappears in swap-t(h)rashing? >The only way to kill it off successfully is to killall >-9 the script name repeatedly. As said earlier, killall -STOP first => keeps the number of processes constant (so he can't spawn any new ones) >Of course, you should always use a bat on the user if nothing else works. ;) Use a keylogger if you distrust, and after a bombing, look who set us up the bomb. Jan Engelhardt -- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/