Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
netikras2659024dSounds like a fun holiday!
Also, check your dimms :) when userspace crashes kernelspace [esp in innocent ways], and especially when random magic starts happening all over the place - it's about time to consider dimm replacement...
Root7279324dAll hail TempleOS.
junon277724dIt's your fault for using the oppressive term "slaves". If you had called them "workers" or "agents" they would have had better self esteem and accepted zone transfers.
This is entirely your fault tbh.
Condor3472823d@junon Hah! NGL after looking at my BIND configs for both for a while, I legit thought that a few times. In the DNS they renamed those to primary/secondary now. RFC8499 is the one to look at for this. ISC in its quest to be as RFC compliant as possible, immediately implemented it... Also ISC is more or less the biggest IETF member in the DNS scene. Paul Vixie - founder of ISC - also wanted to call it initiator/responder.. confused yet? There was a whole naming contest when I brought it up on the DNSOP mailing list, and as you could probably imagine, I was immediately labeled a racist for wanting to get back to master/slave :')
Oh well.. Good thing that I did all 3 DNS servers (1 hidden master, 2 public slaves) complete with zones and configs in git, with a branch for each. So I was able to just check out the slaves' repos to that of the master and restart the service, as if nothing happened. Still gotta figure out why though... That master really shouldn't be as useless as it is now.