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

List:       olpc-bugs
Subject:    Re: #2616 HIGH Update.: Shutdown doesn't stop running activities
From:       "Zarro Boogs per Child" <bugtracker () laptop ! org>
Date:       2008-05-31 22:44:23
Message-ID: 044.906e6da21c1da436346b500eb52a4245 () laptop ! org
[Download RAW message or body]

#2616: Shutdown doesn't stop running activities
---------------------+------------------------------------------------------
  Reporter:  morgs   |       Owner:  Collabora         
      Type:  defect  |      Status:  new               
  Priority:  high    |   Milestone:  Update.2          
 Component:  sugar   |     Version:  Git as of bug date
Resolution:          |    Keywords:                    
  Verified:  0       |    Blocking:                    
 Blockedby:  4877    |  
---------------------+------------------------------------------------------

Comment(by AlbertCahalan):

 Replying to [comment:2 morgs]:
 > When shutting down, we need to stop the running activities, especially
 shared ones as Buddy-Left isn't sent currently.
 >
 > Also it would allow the activities to save in the Journal.

 This is a bad idea.

 Because a power loss can happen at any time, you must always be prepared
 for it. If you have code to do a shutdown, then you have two separate ways
 to quit. One of them will be less used, and thus very likely to be buggy.
 If you are prepared for power loss, as you should be, then it is perfectly
 OK to shutdown by cutting power. It is in fact desirable, because this
 lets you eliminate a huge chunk of shutdown code. (when not really cutting
 power, send the SIGKILL signal)

 Eliminating that code will save power, improve shutdown performance
 greatly, and eliminate the possibility of bugs that occur when a
 "graceful" shutdown is interrupted by power loss.

 Buddies will just have to cope. They must do so anyway. As above,
 elimination of graceful shared activity exit will cause a reduction in
 code and will cause the remaining code to get better testing.

-- 
Ticket URL: <http://dev.laptop.org/ticket/2616#comment:8>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system

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