On Tue, 30 Apr 2019 at 13:44, Sam Ruby <ru...@intertwingly.net> wrote: > > Just a perspective from the one who set up whimsy vm 1 though 4. When > I was setting up whimsy 3 and 4, I updated those scripts to send data > to whimsy n-1 and n. Once the setup was completed, I removed n-1 from > the instructions.
Yes, though it's not how listmodsubs.sh is set up currently. [That can be fixed.] > The issue is one of timing. If one copies over the contents of > various directories, and then later updates the DNS, there may be > missing updates. There is only a single directory involved here: /srv/subscriptions The scripts are run every hour, and the output replaces whatever was there before. So whilst the data might be stale immediately after DNS changeover, it will soon be updated. I don't think there is any data that can be permanently lost here. However it does occur to me that it's possible that the rsync might fail to work initially on the new host. Probably best not to discover that first on DNS changeover... So I propose now to ensure listmodsubs.sh uses the same approach as whimsy_qmail_ids.sh (and document the reasoning) > - Sam Ruby > > On Tue, Apr 30, 2019 at 8:12 AM sebb <seb...@gmail.com> wrote: > > > > There are two cronjobs on hermes that copy data to whimsy: > > > > listmodsubs.sh > > - copies data files to whimsy.apache.org:/srv/subscriptions/ > > > > whimsy_qmail_ids.sh > > - writes data to whimsy-vm4.apache.org:/srv/subscriptions/qmail.ids > > > > It would be nice if there were no need to update these scripts when > > the Whimsy VM is updated. > > > > I propose to update whimsy_qmail_ids.sh to use the generic address. > > Both scripts would then only send data to the current master server. > > > > For testing the new server, one can just copy over the contents of > > /srv/subscriptions. > > > > When DNS is flipped, hermes would start to update the new master. > > > > Does that make sense? > > > > S.
