From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <95dfc7de0701080729u26528609gc332ec5f4d4aeee7@mail.gmail.com> Date: Mon, 8 Jan 2007 10:29:04 -0500 From: "Myron Cheung" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: [9fans] Re: qemu + date/time + plan9 In-Reply-To: <1168251682.016576.324200@42g2000cwt.googlegroups.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_37098_20333758.1168270144250" References: <1168228503.178437.139220@42g2000cwt.googlegroups.com> <1168251682.016576.324200@42g2000cwt.googlegroups.com> Topicbox-Message-UUID: fe840318-ead1-11e9-9d60-3106f5b1d025 ------=_Part_37098_20333758.1168270144250 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline I had this problem a while ago, and if I remember correctly, I fixed it by modifying /rc/bin/termrc which calls aux/timesync . I changed TIMESYNCARGS=-rLa1000000 to TIMESYNCARGS=(-n pool.ntp.org ) . Of course, all this assumes that you have your network operating properly. ------=_Part_37098_20333758.1168270144250 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline I had this problem a while ago, and if I remember correctly, I fixed it by modifying /rc/bin/termrc which calls aux/timesync .

I changed  TIMESYNCARGS=-rLa1000000  to TIMESYNCARGS=(-n pool.ntp.org ) .

Of course, all this assumes that you have your network operating properly.


------=_Part_37098_20333758.1168270144250--