On Tue, 2006-03-07 at 14:49 -0800, Jonathan Day wrote: > Hi, > > I've been running into problems with Linux totally > locking up during extremely large updates. This leaves > the state of the update indeterminate and the state of > RPM's database a complete mess. > > Obviously, there are lower-level issues that need to > be fixed elsewhere. However, what would be truly > valuable would be the addition of either: > > a) --recover (which would analyze the yum cache and > RPM database to determine where yum had got to, then > resume from that point) > > or > > b) --checkpoint and --restore (where --checkpoint > tracks enough details of the progress that --restore > can continue from where it left off) This is something that I've been working on - basically creating a log of the transaction and the events that have been executed so that the transaction can be resumed at the point in which it stops. I don't have an ETA yet, but it's coming along. -- Dennis