kjac,
I encountered a problem tonight that I hope you can help me with.
The power went out at my daughter's place and when it was restored the Replay hung during the reboot. I've encountered this myself from time to time if WiRNS is not running when the Replay boots up. With WiRNS 0.7a it was no problem as you could just start WiRNS, reboot the Replay, and all would be fine.
The conundrum occurs with 1.1.x as it waits at "Refreshing RecordingGuide for: xxx" trying to load the Replay Guide before it runs micro.dns. But the Replay won't finish booting until micro.dns is running. Stalemate!
Eventually (and I mean a long time) one of them, I'm not sure which, gives up and then WiRNS finishes. Rebooting the Replay then completes normally.
My question, would it be possible to change to load order and have WiRNS refresh the record guide after running micro.dns rather than before?
Thanks,
Jim
I encountered a problem tonight that I hope you can help me with.
The power went out at my daughter's place and when it was restored the Replay hung during the reboot. I've encountered this myself from time to time if WiRNS is not running when the Replay boots up. With WiRNS 0.7a it was no problem as you could just start WiRNS, reboot the Replay, and all would be fine.
The conundrum occurs with 1.1.x as it waits at "Refreshing RecordingGuide for: xxx" trying to load the Replay Guide before it runs micro.dns. But the Replay won't finish booting until micro.dns is running. Stalemate!
Eventually (and I mean a long time) one of them, I'm not sure which, gives up and then WiRNS finishes. Rebooting the Replay then completes normally.
My question, would it be possible to change to load order and have WiRNS refresh the record guide after running micro.dns rather than before?
Thanks,
Jim















