Before I try to complete a final incremental backup and shut it down, I would like to get a question out there. I apologize in advance for asking without doing a thorough search of the archives first.
When I suggested making the atime in Bayes two bytes instead of four by making it coarser grained than one second, somebody (Justin?) said that it had been tried and produced problems in handling expiry.
Can whoever knows about this post some details? It would make such a difference in I/O requirements to not have to update the atime field on every significant token in every message, that I don't want to just drop the issue without trying to solve the problems with it. I have a hard time imagining what would be wrong with expiring tokens on a day boundary instead of one second.
Thanks, and wish me luck on the laptop.
By the way, Toshiba doesn't make the Satellite Pro 6100 anymore, but if you ever have a chance to get one, run the other way.
-- sidney