[Yum-devel] What to do about yum-updatesd?

Jeremy Katz katzj at redhat.com
Mon Jul 23 15:58:06 UTC 2007


On Fri, 2007-07-20 at 13:29 -0400, Matthew Miller wrote:
> On Thu, Jul 19, 2007 at 08:32:43PM -0400, Jeremy Katz wrote:
> > > On Thu, Jul 19, 2007 at 03:23:32PM -0400, Jeremy Katz wrote:
> > > >   1) yum-updatesd.  Daemon that sits on dbus brokering off requests
> > > Could this part be oddjobd?
> > Actually talked with Nalin about it yesterday on the way home, but
> > oddjob doesn't give us periodic activation, having the helper be a
> > singleton, the caching that we're doing, and a few other things
> 
> I think periodic activation is best handled by cron, insomuch as that's what
> it's there for. Some very tiny script called from cron can send the "go now"
> signal. I'd really like to avoid the proliferation of system-helper daemons,
> particularly when we've got parts that already would be able to do most of
> the work. The Unix Way and all that.

Except that cron sucks a lot for systems which aren't always on.

Also, it's kind of a moot point here because until the old dbus
interface of yum-updatesd completely goes away, we have to have a daemon
to be able to handle some of the compatibility fun.

Jeremy




More information about the Yum-devel mailing list