Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932332AbVKKBMV (ORCPT ); Thu, 10 Nov 2005 20:12:21 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932333AbVKKBMV (ORCPT ); Thu, 10 Nov 2005 20:12:21 -0500 Received: from tantale.fifi.org ([64.81.251.130]:20383 "EHLO tantale.fifi.org") by vger.kernel.org with ESMTP id S932332AbVKKBMU (ORCPT ); Thu, 10 Nov 2005 20:12:20 -0500 To: Dick Cc: linux-kernel@vger.kernel.org Subject: Re: SIGALRM ignored References: <20051107160332.0efdf310.pj@sgi.com> <87hdamk56f.fsf@ceramic.fifi.org> <87r79pboxx.fsf@ceramic.fifi.org> Mail-Copies-To: nobody From: Philippe Troin Date: 10 Nov 2005 17:12:17 -0800 In-Reply-To: Message-ID: <87k6fgq972.fsf@ceramic.fifi.org> User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 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: 831 Lines: 18 Dick writes: > Philippe Troin fifi.org> writes: > > Look at the display manager. I know that wdm used to not clean up its > > signals before starting a user session. > > I've found the error, the signal was blocked in sshd and I was restarting sshd > from a ssh session, I also disabled some pam modules (which I suspect the block > came from). Restarting sshd from a console did the trick. Daemons like ssh should clean-up their signal masks on start-up. Maybe you should file a bug against ssh? > I don't know how to thank you ;-) Then don't :-) Phil. - 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/