On Wed, 2010-06-16 at 12:26 -0400, seth vidal wrote: > On Wed, 2010-06-16 at 10:22 -0600, Jason L Connor wrote: > > On Wed, 2010-06-16 at 10:44 -0400, Jason Dobies wrote: > > > Anyone have any ideas? > > > > Another idea is to skip using cron altogether and perhaps adapt kronos > > to our needs. > > http://www.razorvine.net/download/kronos.py > > > > That looks like it would require pulp to be a daemon running all the > time? > > So you'd be reimplementing cron inside pulp. > > As a sysadmin I'd not like that. > > -sv > >
There is a portion of pulp, called 'juicer' that potentially runs all the time as part of apache. I do like the notion of reusing cron. However, if there are technical obstacles, we should consider alternatives. Kronos is part of the turbo gears framework and should be reasonably well fleshed out. As an admin, I don't think I'd care too much how it was implemented, just that it worked. Though, I would like to get more feedback on that. -- Jason L Connor Senior Software Engineer Systems Management and Cloud Enablement Red Hat, Inc. +1.919.890.8331 Freenode: linear
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
