So the house got momentarily power-cycled this morning… I’m at work, minding my own business, next thing the access point emails me this:
Mar 13 09:04:23 Syslogd start up
Now, it only does that for two reasons. Either someone told it to reboot (not I), or it got hard reset. Sure enough, log into the old server, and it’s reporting an uptime of 15 minutes. I get home this evening, and clocks all around are on the blink … literally.
The cluster course is going, power outage? What power outage?
I did consider wiring up the ADSL modem, router, study switch, and the TS-7670 up to the cluster’s power rails, but haven’t gotten around to doing that. Alas, I’m not quite there yet.
In any case, even if the TS-7670 had been powered from the solar, I’d have still have temporarily lost the build as the HDD dock I have the hard drive sitting in is mains powered. It also doesn’t remember its state after a power cycling. I’d have re-started the build from work, but the HDD remained off when the power came back on.
Never mind. The downside is now I get to re-start a multi-day build. The good news though, is that knowing the ebuild file that Portage picked out for compiling gcc; I can resume where it left off. In this case, it’s using an ebuild from the musl overlay; /root/musl/sys-devel/gcc/gcc-6.4.0-r1.ebuild.
ebuild /root/musl/sys-devel/gcc/gcc-6.4.0-r1.ebuild package will preserve the current working tree and will resume where it was, hopefully without incident. I’ll be left with a .tbz2; which will be picked up when I run emerge –keep-going -ekv @system.