From: Philippe Troin <phil@fifi.org>
To: Dick <dm@chello.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SIGALRM ignored
Date: 10 Nov 2005 17:12:17 -0800 [thread overview]
Message-ID: <87k6fgq972.fsf@ceramic.fifi.org> (raw)
In-Reply-To: <loom.20051110T210222-252@post.gmane.org>
Dick <dm@chello.nl> writes:
> Philippe Troin <phil <at> 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.
next prev parent reply other threads:[~2005-11-11 1:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-07 17:36 SIGALRM ignored Dick
2005-11-08 0:03 ` Paul Jackson
2005-11-08 12:00 ` Dick
2005-11-09 0:58 ` Philippe Troin
2005-11-09 9:21 ` Dick
2005-11-09 19:28 ` Philippe Troin
2005-11-10 20:04 ` Dick
2005-11-11 1:12 ` Philippe Troin [this message]
2005-11-08 2:35 ` Keith Owens
2005-11-08 11:48 ` Dick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k6fgq972.fsf@ceramic.fifi.org \
--to=phil@fifi.org \
--cc=dm@chello.nl \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox