From owner-freebsd-questions@FreeBSD.ORG Wed Mar 8 16:24:46 2006 Return-Path: X-Original-To: questions@freebsd.org Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 38CAE16A420 for ; Wed, 8 Mar 2006 16:24:46 +0000 (GMT) (envelope-from dgw@liwest.at) Received: from lilzmailso01.liwest.at (lilzmailso01.liwest.at [212.33.55.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id D2A8143D46 for ; Wed, 8 Mar 2006 16:24:45 +0000 (GMT) (envelope-from dgw@liwest.at) Received: from cm56-136-28.liwest.at ([86.56.136.28] helo=[192.168.1.102]) by lilzmailso01.liwest.at with esmtp (Exim 4.44) id 1FH1Su-0004nE-5N for questions@freebsd.org; Wed, 08 Mar 2006 17:24:44 +0100 From: Daniela To: questions@freebsd.org Date: Wed, 8 Mar 2006 17:22:42 +0000 User-Agent: KMail/1.5.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603081722.42346.dgw@liwest.at> X-Spam-Score: -0.9 (/) X-Spam-Report: BAYES_30=-0.904 Cc: Subject: Signal 17 to Fluxbox -> system lockup X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dgw@liwest.at List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Mar 2006 16:24:46 -0000 Hi list! Over the years I got into the habit of suspending processes with signal 17 (SIGSTOP). And everything ran fine until yesterday: I suspended Fluxbox and after switching to it's VTY I couldn't switch back, the system didn't respond any more to my keyboard input. How can I prevent these lockups (besides the obvious), i.e. how do I prevent Fluxbox from intercepting certain key combinations (Control + Alt + F[n])? Thanks in advance. Daniela -- Hope is the worst of all evils, for it prolongs the torments of man.