[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RP] ratpoison on CDE
From: |
Peter Pentchev |
Subject: |
Re: [RP] ratpoison on CDE |
Date: |
Sun, 7 Jan 2001 18:43:13 +0200 |
User-agent: |
Mutt/1.2.5i |
On Sat, Jan 06, 2001 at 02:30:41AM -0800, shawn wrote:
> >
> >Hi all,
> >
> >I'd sent mail yesterday about a problem I was having running ratpoison
> >under CDE. It appears that for some reason the SIGALRM's that
> >ratpoison uses to close the window list was causing the ratpoison proc
> >to die. The code tries to install some handlers for SIGALRM, so I'm
> >not sure what is going on here. I wrote a script to swallow SIGALRM
> >and SIGHUP before running ratpoison. So I have to deal with a window
> >list that never closes, but I don't care. I may be able to look into
> >this more later, but maybe not. Anyway, thanks.
>
> This SIGALRM problem has also sprung up for other people. It seems
> like a somewhat flaky way to do it anyway. This is code from the good
> ol' "If I could just get this last feature in, no matter how I do
> it...". If anyone has a better idea, I'd love to hear it!
I think handling it with SIGALRM is a nice idea, granted that sigaction()
(POSIX-standardized) is used instead of signal() (quite dangerous due to
this very 'handler reinstalled' ambiguity). Another way to do this could
be a window-list thread, but multithreading support just for the windowlist
is a bit of an overkill IMHO :)
Just see that somebody doesn't try to use/raise/ignore SIGALRM for some
other use in the future RP development :)
G'luck,
Peter
--
What would this sentence be like if it weren't self-referential?