Hi, > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of ext Marcel Holtmann > Sent: Thursday, February 03, 2011 1:13 AM > To: [email protected] > Subject: RE: [RFC 2/2] doc: Add description for history agent interface > > > > So yes, there might be conditions where you crash before fsync > really > > > completes and you lose the SMS. However, there's nothing in the > world > > > you can do about this case anyway, since both the write and the > fsync > > > succeeded. > > > > I think this is perfectly reasonable. Even if some storage system > > had some internal caches outside the kernel sync's reach, I'd imagine > > flushing these would be a prime candidate for last-minute actions > done > > before battery dies (or some sensor detecting the device is about to > > hit a brick wall in about a few milliseconds ;)). > > so the device health or charging daemon or whatever will most likely > shut down the device cleanly before the battery dies completely. The > case that a device suddenly dies, because the battery is empty does not > really exist.
Obviously you never dropped a phone on the floor so luckily that the battery pops out :) There are also kernel crashes, and I wouldn't always trust the system daemons to perform a graceful shutdown. There is no excuse to not using reliable persistence mechanisms when 1) they are readily available; 2) their usage is mandated by certification requirements. Best regards, Mikhail _______________________________________________ ofono mailing list [email protected] http://lists.ofono.org/listinfo/ofono
