Hi Chris, here in Lima, I'm debugging a problem that the local team has shown me with the wilkipedia activity not starting for a second time. The problem is that the server never really closes, so the 2nd invocation finds the socket taken, and can't use it. Apparently this is a common issue with SimpleHTTPServer.
We need to be able to close the server when the app closes. I am starting to work on this - but can't get on irc, fascist fw - so if you ahve anyhint, welcome :-) So far my plan is to - learn what signal/event we get from Sugar when the app is closed (do we get one?). I'm *so* not a Sugar developer ;-) - Try if a SIGHUP or SIGTERM will bring it down cleanly - if so, try and send one to the process on close - If signals are not the way, try the recipe at http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/336012 Ah, I see that there's a known bug and some recent patches for it: http://dev.laptop.org/git?p=projects/wikiserver;a=summary - do we know what version of the code is in Peru's 703-5 image? cheers, m -- [EMAIL PROTECTED] [EMAIL PROTECTED] -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff _______________________________________________ Devel mailing list [email protected] http://lists.laptop.org/listinfo/devel
