On Tue, 2007-07-03 at 23:25 +0300, Panu Matilainen wrote: > --- > If you want ^C handling in yum the choices are (as I've told you before): > 1) being careful about when the database is opened. > 2) exposing the same signal bit mask to the bindings so that ^C can be > detected whenever. > Other alternatives include > 3) adding infrastructure to chain signal handling out of rpmlib. > --- > > Yum is now in far better shape for 1) than it was before, because it > doesn't have to download tons of headers and feed into rpm for dep > resolution. The last time we tried 1) we got blamed for corrupting the rpmdb, over and over and over again. Your thoughts on that debacle?
> Adding proper signal handling/passing, be it 2) or 3) or whatever variant > I'm going to look into anyway. okay - b/c if we're just in a readonly db and we get a sigterm - that's fine. > Oh and then there's another locking related issue I just noticed when > looking at this: yum (and any related code like plugins, pirut etc) > tracebacks can leave stale rpmdb locks around. I suppose yum could insert > a global exception handler whenever a ts is active to clean up any rpmdb > accesses. I'm going to have a look at mopping up the locks on tracebacks > at bindings level anyway, and sooner than later I hope. okay - I think that's where I'd rather see it go. That and have fewer places where we actually need the rpmdb at all. -sv _______________________________________________ Yum-devel mailing list [email protected] https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
