From: Theo de Raadt Subject: Re: Clarify -f option in dbupdate(8), tune -n To: ajacoutot@bsdfrog.org, deraadt@cvs.openbsd.org Cc: cs@schulte.it, stu@spacehopper.org, tech@openbsd.org Date: Sun, 1 Nov 2026 07:33:48 -0600 >On Sun, Nov 01, 2026 at 07:01:13AM -0600, Theo de Raadt wrote: >> My plan for dbupdate is to run it from the _weekly_ script (since TZ >> updates have historically always had at least 1 week heads up even from >> the most retarded governments), and I suspect this will also cover >> problems with certs quickly enough. >> >> Users can always run it manually themselves, in which case the weekly >> run will notice it does not need to do the large download operation. >> On that matter: >> >> I am not seriouslyu concerned about having all openbsd machines in timezone >> stripe hitting downloads for (typically) a single file at the same time, >> if I change it to use cdn.openbsd.org >> >> I am considering whether the installurl mirror should be used, or if >> it we should make it use the cdn (for the potential pressure)... >> >> Maybe try to use the cdn first, failover the installurl. It is possible >> someone will run an underbuilt mirror because too many users end up >> pointing at it without them knowing. The cdn is much better prepared >> to handle this. > >I am not concerned about this. >Mirrors already get their fair share of pkg_add -un and syspatch -n. And I am >not talking about all the rsync or http mirror syncs. The mirrors do not experience everyone in the same TZ band hitting them in roughly the same second. Do they? (And I do not want to use ~ to work around that). People expect the big script to run at a known time. I also don't want the timezone offset to change asyncronously while one of these scripts is running with a seperate cron statement. It is better if it changes syncronouslyinside the script.