>>>>> On Sat, 13 Mar 2010 11:04:20 -0600, "Joseph A. Counsil" >>>>> <[email protected]> said:
> David, > This might be a good option for some - in cases where there is not a > live network connection where NTP can be used to automatically update > the time. For those of us who usually have a network connection, it can > be disabled. > For instance, during Field Day, we don't have a network connection at > our remote location, and it would be good to verify accurate time. Keep in mind that the clock won't drift all that much during periods of no internet connectivity. If your clock was correct before the emergency, it should still be close enough to generate accurate timestamps at minute/second resolution. Unless your CMOS battery is dead, as Mike said, but in my experience that's quite rare even with very old machines. Further, the NTP client will learn and remember your system's clock drift, and correct it even when there are no reachable servers. Note 1: this applies to proper NTP clients, not SNTP clients that simply wake up every so often and set the clock to whatever the server says the time is. Note 2: during field operation, the drift characteristics will probably change because of different temperatures etc... but I think I'm nitpicking now. If the emergency lasts long enough that clock drift becomes an issue, just use any GPS receiver with a time readout to get within < 1s of UTC. -- 73, Stelios, M0GLD. _______________________________________________ fldigi-alpha mailing list [email protected] https://lists.berlios.de/mailman/listinfo/fldigi-alpha
