If you agree with "put up or shut up" then please PUT UP or just SHUT UP!
You haven't given anything to the community, so please don't expect anything in return. If you wish to see your version of reliable and secure become the norm, then we welcome examples we can all try.
My point about NTP is this, you expect, nay demand, perfection in software, and then you put up with cruddy hardware. But you expect that the software should be able to compensate for the hardware and that is alright. Of course a truly high quality NTP system never has that problem because it is in fact MONOTONIC and the small corrections that may be required to adjust the time, if done often enough will ensure that even the pretty bad clocks we see in computers right now can be kept in line. Of course it is well understood that even NTP 4, being deployed now, does not overcome all of the potential problems which have already been identified. So at some point we KNOW that NTP on faster machines with rapidly decresing measurement latency and vastly increased resolution WILL FAIL.
As for clock_gettime(CLOCK_MONOTONIC) - just use Google. Sadly, all that CLOCK_MONOTONIC will give you is a MONOTONIC clock. It makes no guarantees about accuracy of tick intervals.
For email:
naturally with all of their dependencies. For front end servers we use qmail and Vpopmail with a single instance of RoboMail. We have not modified ANY of the CPAN Modules.
jdtoronto
| [reply] |
