ctly, f.y.i.) about setting up a network-wide ntp
server with openings in the firewall (probably a good idea to run this
in the DMZ area, not on the internal net), or get a clock-sync device
like a GPS or Atomic Clock receiver, and sync through that.
Regards,
--
Svein Skogen| Mobile Pho
ny and all input welcomed.
Regards,
Svein Skogen
--
Svein Skogen| Mobile Phone: +47 907 03 575
Solberg Østli 9 | [EMAIL PROTECTED]
2020 Skedsmokorset | PGP Key: 0xE5E76831
Norway | RIPE handle: SS16503-RIPE
+--
doesn't need
to traverse the NAT rules when communicating with the external NTP
servers, the NAT latency won't add to it), and it will reduce traffic
overall.
Just hope I didn't confuse the topic too much.
//Svein
--
Svein Skogen| [EMAIL PROTECTED]
Solberg
g except shoveling packets takes the back
seat.
//Svein
--
Svein Skogen| [EMAIL PROTECTED]
Solberg Østli 9 | PGP Key: 0xE5E76831
2020 Skedsmokorset | [EMAIL PROTECTED]
Norway | PGP Key: 0xCE96CE13
+---
powers the chip from the
mainboard, and connects the TX/RX wires there. Using standard NMEA
protocol, and knowing the latency of the port itself, it can give me a
fairly good, and simple to maintain, clock. It won't be perfect, but it
won't perfectly break my bank account eighter.
//S
cision to outlive our current perspective?
I know that such a change will in parts increase the complexity of the
current codebase, and I know that there are plenty on this list that can
refine this idea (or give a very good explanation why this is stupid :)
), but can we atleast consider it?
Re
indows introduces some synthetic
limitations on different "breeds" (editions) of the OS. Linux doesn't.
//Svein
--
Svein Skogen| [EMAIL PROTECTED]
Solberg Østli 9 | PGP Key: 0xE5E76831
2020 Skedsmokorset | [EMAIL PROTECTED]
Norway | PG
nt
ntpdate gone totally. This is a problem I'm afraid noone here can help
them with. If they have religious reasons for wanting something done or
gone, I suggest talking to a cleric about them. Sorry if I've insulted
anybody with this.
Just my ?0.02
//Svein
- --
- +---
