On Sat, Jun 03, 2006 at 05:15:13PM -0400, Anthony DeRobertis wrote: > Marc Haber wrote: > >Is there any way to reproduce this without deliberately crashing an X > >session? > > Probably. Reading the bug report, it sounds like there is a known race > condition that may cause this. I suspect that whatever sequence my X > clients died in hit the race condition. The xterm probably started to > exit, leading to reads failing. debfoster probably took the read failure > as me hitting enter (e.g., the default) and kept going. Then it probably > got a SIGTERM. > > I'd guess that an appropriately-timed SIGKILL could reproduce it. Or > maybe just hitting the close box in the xterm its running in.
I tried hitting the closebox of the xterm while debfoster was sitting at a query prompt, and my keepers file survived. > >Asides from that, I agree that debfoster should write new keepers to a > >tempfile. > > I think that the ftruncate in writekeepers is very likely the cause of > this bug. Fixing that function to do things the Right Way(tm) with a > tempfile and rename(2) should fix it. Probably, yes. Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
