[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: KFM: final touch
From:       David Sweet <dsweet () chaos ! umd ! edu>
Date:       1998-12-10 13:37:00
[Download RAW message or body]

On Wed, 09 Dec 1998, Andreas Pour wrote:
>David Sweet wrote:
>
[...]
>>
>> This solution might be more difficult, but how about keeping them in
>> /tmp and making two changes:
>>         1) check to see if the named socket still exists before using it,
>>         if not, set up a new one
>>         2) delete them when kfm exits OR is killed -- this second part is
>> important!  I usually get /tmp/kfm*'s laying around when I CTRL-ALT-BS
>> an X session.
>
>Well, when a process gets killed by X being Ctl-Alt-Bs'd, it gets no warning.  The
>only thing kfm do is when it first loads check for stale sockets (that would work only
>if you can tell the difference between a stale socket and one being used by another
>instance of kfm).
>
>Regards,
>
>Andreas Pour
>pour@mieterra.com

For #1 I was thinking more of signal() or sigaction() -- I think any signal
(except kill -9 -- ?) can be caught that way and and some function would
be called which could clean up.

Dave

[prev in list] [next in list] [prev in thread] [next in thread]