On Wed, 2007-10-31 at 10:20 -0400, Jeremy Katz wrote: > On Wed, 2007-10-31 at 09:52 -0400, seth vidal wrote: > > On Wed, 2007-10-31 at 09:50 -0400, Jeremy Katz wrote: > > > On Wed, 2007-10-31 at 13:29 +0100, Tim Lauridsen wrote: > > > > Luke Macken wrote: > > > > > On Mon, Oct 29, 2007 at 03:26:49PM -0400, Jeremy Katz wrote: > > > > > > So my concern with this is that if we're in the middle of installing > > > > > > updates, this is going to leave your system in a really bad place. > > > > > > :-/ > > > > > > > > > > True. How did the monolithic daemon handle this ? > > > > > > > > Can't this be done by checking if /var/run/yum.pid exist and contains > > > > the pid of the yum-updatesd-helper > > > > if this is the case the don't kill, else just waste it. > > > > > > When is it ever going to be running but not be the pid > > > in /var/run/yum.pid? I mean, there's a slight window I guess but it's > > > not that relevant > > > > > > > I didn't think it grabbed the lock for its ENTIRE run, I thought it just > > had it when it was doing something. > > The helper isn't ever running unless it's doing something... >
Ah, sorry, I was thinking of yum-updatesd. So we can't shut down the helper, obviously but we can check for the difference and emit something intelligent. if helper_is_not_running: exit nicely else: say something about your mom, why you should leave the helper alone -sv _______________________________________________ Yum-devel mailing list [email protected] https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
