On Sun, 24 Feb 2008 11:29:06 +0100 [EMAIL PROTECTED] (Lars Munch) babbled: > On Sun, Feb 24, 2008 at 07:48:03PM +1100, Carsten Haitzler wrote: > > On Sun, 24 Feb 2008 15:43:18 +1100 Carsten Haitzler (The Rasterman) > > <[EMAIL PROTECTED]> babbled: > > > > actually - found a problem. breaks entrance it seems and enlightenment when > > init is enabled! :) back! > > Thanks for testing, too bad it didn't work out as expected. I do not use > entrance and have init disabled in enlightenment, so everything was > working flawlessly here :/ > > Anyway, I just did some more testing. It seems that using pselect we > have a bigger chance of losing signals. If we get the same signal > twice, while not waiting in the pselect call, then only one signal will > be handled at the time pselect is called. I guess this could cause the > breakage. Do you think that's the issue (I don't know the entrance nor > the init code) ? > > I have no idea how to solve this, except for going back to the pipe > solution.
entrance and e both use signals. entranced waits for SIGUSR1 from x to know x is ready. e waits for something similar with a pause() from the init splash process. no singal ever arrives. pause() is never interrupted :) -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [EMAIL PROTECTED] ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
