Adam Chlipala wrote: > What a big old smelly coincidence that we have to deal with two of these > failures so close together.... > > I agree that it doesn't make sense to attempt any repairs that end with > Abulafia back at Xiolink. Abulafia is still fulfilling an important > role: during the periods when fyodor was down, it was important to > retain Abulafia's secondary DNS services. Thus, I think it would be > best to get Abulafia up at Peer 1 with its exact current configuration > and change the ns2.hcoop.net IP address at our registrar. > > I continue to recommend not thinking about re-configuring Abulafia for > its intended role at Peer 1 until after we have deleuze and mire working > properly with everyone migrated. > > ntk, are you volunteering to do all of the work of getting Abulafia > running again once it reaches Peer 1? > > Any objections from anyone to this general course of action? > Fine by me, but whether or not I get it working, it's better that it sit unused at Peer1 than sit unused at Xiolink, because in the second case we are paying monthly for the privilege and ultimately we will want to get it online at Peer1 so we'd have a head start. But I think it should be easy to get Abu back online once I have physical access.
I was thinking about ordering a replacement disks in advance but I guess I should take a look at abu first to ensure that the disk is actually failed. Anyway I say go ahead and tell xiolink to ship the machine out. -ntk _______________________________________________ HCoop-SysAdmin mailing list [email protected] http://hcoop.net/cgi-bin/mailman/listinfo/hcoop-sysadmin
