lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <20B28DA2-26BB-11D9-8B7A-000D93C0F38C@teknovis.com> From: andfarm at teknovis.com (Andrew Farmer) Subject: Windows Time Synchronization - Best Practices On 24 Oct 2004, at 18:48, Gary E. Miller wrote: > On Fri, 22 Oct 2004, Micheal Espinola Jr wrote: >> You can certainly have multiple time servers specified with Windows >> Time Service (SNTP). RTM. It has the ability to failover through a >> list. > > Yes you can have multiple time servers, but only one active at a time. > With NTP your client polls a number of diverse servers. Routes can > flap, servers can go wacko, but your time stays solid. The canonical *NIX ntp client supports multiple active servers, if that's what you're talking about. No idea about Windows, though. -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20041025/62cb8aa0/PGP.bin
Powered by blists - more mailing lists