On Fri, 2005-01-21 at 15:44 -0500, dopry wrote: > Why not handle it through update-data.sh?
I do, actually. That's what happens as a result. I've changed that not to actually run make though, it also sets a flag. Under the circumstances, I can't have multiple things running that are under the assumption they have sole control over tinydns. So rather than running update-data.sh through cron, I have another script that runs from cron and looks after all the bits of my tinydns, tinydyndns, and dnscache. As far as VegaDNS is concerned, the change is small. Instead of cron running a job that dumps the zones to see if anything has changed, I don't run the job unless something _has_ changed. I could have continued dumping and comparing zones out of VegaDNS every 5 minutes in update-data.sh like I had been (impatient users), but that just seems ugly to me. I realize doing it my way probably seems ugly to you though. VegaDNS was obviously meant to take over the role of tinydns front-end rather than to supplement the existing method, however, it happens to work well for me that way. - Ron
