Brock Pytlik wrote: > Shawn Walker wrote: > >> Padraig O'Briain wrote: >> >> >>> The webrev http://cr.opensolaris.org/~padraig/ips-5873-v1/ fixes >>> bug 5873 - No need to refresh catalogs when installing a package. >>> >>> >> 1) you shouldn't assume people are running updatemanager or the cron >> refresh thing >> The cron refresh task is installed and setup by the update service. If you are running the PM then you should certainly be running this cron job. I agree that someone could turn it off but this seems a little odd to say the least, why would they, how would the ordinary user even know what to turn off, let alone do it.
To guard against this we can certainly check that this service is online and if it isn't then drop back to a refresh on startup. >> 2) we specifically made the change to have the system automatically >> refresh catalogs during install, etc. some months ago >> >> 3) changing this behaviour would mean the cli/gui no longer have >> consistent behaviour >> >> However, I could be convinced that you could skip this if you perform a >> catalog refresh at least once at some point after startup or on the >> first install/update. We should not be relying on any other program >> (such as updatemanager) that may or may not be running to do this. >> >> Arguably, if the performance of refresh catalog is the issue, I'd rather >> fix that. It should be a relatively quick operation. >> >> Looking for feedback from other team members. >> >> Cheers, >> >> > I agree, blindly assuming that the catalogs are current is the wrong > approach. > Stephen has some thoughts on an authority giving the client > guidance on how often it should be refreshed, but I'm not certain what > time frame that's going to happen on. Would be great to have this, but in the meantime: If we check at startup that the last catalog refresh happened within the last 10 hrs then we should be fine (we could have the refresh task store this last update time for us in gconf if need be). If it has not then we can refresh the catalog on startup. If we want to make sure things are ok for a long running package manager, we just repeat the check once a day as you suggest and if the cron job is operational we will never need to do the refresh as its been done for us. 0.30 9.30 12.30 18.30 21.30 > I don't think refreshing only at > start up is adequate either since someone may start package manager and > leave it running in the background for days or weeks. Until the > authority has more guidance on refresh rate, I would be alright with the > package manager tracking its last refresh and refreshing at start up, > and then again if the last refresh was over one day ago. (Why one day? > Cause it just seems like a reasonable period to me for now. If someone > wants to argue for 6 hours, or 2 days, I wouldn't really have objections.) > > Brock > _______________________________________________ > pkg-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/pkg-discuss > _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
