[9fans] timesync -r not working?

[9fans] timesync -r not working?

[Ethan Grammatikidis]

I'm running plan 9 in qemu, I want to use the qemu-emulated hardware clock for the plan 9 time because it keeps the same time as the host.

I made a script to be sourced from cpurc:

	#!/bin/rc

	echo '> starting timesync'

	if (! test -e '/dev/rtc')
		bind -a '#r' /dev
	aux/timesync -r

The script runs at boot, the echo tells me that much, but the time is not set, perhaps as if timesync -r is not working. To be specific the date a few minutes after booting is Sun Jan  2 18:30:36 GMT 2000.

Should I not use timesync at all? I ask because $boottime (which is set before timesync is started) contains a reasonable date.

--
Ethan Grammatikidis
The lyf so short, the craft so long to lerne. -- Chaucer

Re: [9fans] timesync -r not working?

[erik quanstrom]

> The script runs at boot, the echo tells me that much, but the time is not set, perhaps as if timesync -r is not working. To be specific the date a few minutes after booting is Sun Jan  2 18:30:36 GMT 2000.

i believe timesync is setting the system clock from /dev/rtc, not the other way
around.

- erik

Re: [9fans] timesync -r not working?

[Ethan Grammatikidis]

On Fri, 26 Jun 2009 15:48:25 -0400
erik quanstrom <quanstro@coraid.com> wrote:

> > The script runs at boot, the echo tells me that much, but the time is not set, perhaps as if timesync -r is not working. To be specific the date a few minutes after booting is Sun Jan  2 18:30:36 GMT 2000.
>
> i believe timesync is setting the system clock from /dev/rtc, not the other way
> around.

Yeah, that's what I expect timesync to do, but it's doing something strange instead.

--
Ethan Grammatikidis
The lyf so short, the craft so long to lerne. -- Chaucer

Re: [9fans] timesync -r not working?

[erik quanstrom]

> > > The script runs at boot, the echo tells me that much, but the time is not set, perhaps as if timesync -r is not working. To be specific the date a few minutes after booting is Sun Jan  2 18:30:36 GMT 2000.
> >
> > i believe timesync is setting the system clock from /dev/rtc, not the other way
> > around.
>
> Yeah, that's what I expect timesync to do, but it's doing something strange instead.

i wouldn't classify doing what the man page says it does
as something "really strange".  if you want the converse,
then just execute "date -n >/dev/rtc".

- erik

Re: [9fans] timesync -r not working?

[John Floren]

On Fri, Jun 26, 2009 at 4:57 PM, erik quanstrom<quanstro@quanstro.net> wrote:
>> > > The script runs at boot, the echo tells me that much, but the time is not set, perhaps as if timesync -r is not working. To be specific the date a few minutes after booting is Sun Jan  2 18:30:36 GMT 2000.
>> >
>> > i believe timesync is setting the system clock from /dev/rtc, not the other way
>> > around.
>>
>> Yeah, that's what I expect timesync to do, but it's doing something strange instead.
>
> i wouldn't classify doing what the man page says it does
> as something "really strange".  if you want the converse,
> then just execute "date -n >/dev/rtc".
>
> - erik
>
>

I'm pretty sure he's *trying* to get the time from /dev/rtc, not
trying to set it.

John
-- 
"I've tried programming Ruby on Rails, following TechCrunch in my RSS
reader, and drinking absinthe. It doesn't work. I'm going back to C,
Hunter S. Thompson, and cheap whiskey." -- Ted Dziuba

Re: [9fans] timesync -r not working?

[Ethan Grammatikidis]

On Fri, 26 Jun 2009 17:39:12 -0700
John Floren <slawmaster@gmail.com> wrote:

> On Fri, Jun 26, 2009 at 4:57 PM, erik quanstrom<quanstro@quanstro.net> wrote:
> >> > > The script runs at boot, the echo tells me that much, but the time is not set, perhaps as if timesync -r is not working. To be specific the date a few minutes after booting is Sun Jan  2 18:30:36 GMT 2000.
> >> >
> >> > i believe timesync is setting the system clock from /dev/rtc, not the other way
> >> > around.
> >>
> >> Yeah, that's what I expect timesync to do, but it's doing something strange instead.
> >
> > i wouldn't classify doing what the man page says it does
> > as something "really strange".  if you want the converse,
> > then just execute "date -n >/dev/rtc".
> >
> > - erik
> >
> >
> 
> I'm pretty sure he's *trying* to get the time from /dev/rtc, not
> trying to set it.
> 

You'd be right.

I've found I don't seem to need timesync, the system time & /dev/rtc alike seem to stay in sync with the host without it, but I'm still curious why timesync -r should mess up the system time so badly.

Perhaps /dev/rtc and the system time are linked on some architectures, so that setting one sets the other and so timesync -r gets in a mess. Just a guess.

-- 
Ethan Grammatikidis
The lyf so short, the craft so long to lerne. -- Chaucer

Re: [9fans] timesync -r not working?

[Federico G. Benavento]

timezones?

On Sat, Jun 27, 2009 at 4:46 AM, Ethan Grammatikidis<eekee57@fastmail.fm> wrote:
> On Fri, 26 Jun 2009 17:39:12 -0700
> John Floren <slawmaster@gmail.com> wrote:
>
>> On Fri, Jun 26, 2009 at 4:57 PM, erik quanstrom<quanstro@quanstro.net> wrote:
>> >> > > The script runs at boot, the echo tells me that much, but the time is not set, perhaps as if timesync -r is not working. To be specific the date a few minutes after booting is Sun Jan  2 18:30:36 GMT 2000.
>> >> >
>> >> > i believe timesync is setting the system clock from /dev/rtc, not the other way
>> >> > around.
>> >>
>> >> Yeah, that's what I expect timesync to do, but it's doing something strange instead.
>> >
>> > i wouldn't classify doing what the man page says it does
>> > as something "really strange".  if you want the converse,
>> > then just execute "date -n >/dev/rtc".
>> >
>> > - erik
>> >
>> >
>>
>> I'm pretty sure he's *trying* to get the time from /dev/rtc, not
>> trying to set it.
>>
>
> You'd be right.
>
> I've found I don't seem to need timesync, the system time & /dev/rtc alike seem to stay in sync with the host without it, but I'm still curious why timesync -r should mess up the system time so badly.
>
> Perhaps /dev/rtc and the system time are linked on some architectures, so that setting one sets the other and so timesync -r gets in a mess. Just a guess.
>
> --
> Ethan Grammatikidis
> The lyf so short, the craft so long to lerne. -- Chaucer
>
>



-- 
Federico G. Benavento

Re: [9fans] timesync -r not working?

[Ethan Grammatikidis]

On Sat, 27 Jun 2009 05:36:55 -0300
"Federico G. Benavento" <benavento@gmail.com> wrote:

> timezones?

I've never heard of a timezone that could make a 9 year difference. Maybe on Pluto. ;)

> 
> On Sat, Jun 27, 2009 at 4:46 AM, Ethan Grammatikidis<eekee57@fastmail.fm> wrote:
> > On Fri, 26 Jun 2009 17:39:12 -0700
> > John Floren <slawmaster@gmail.com> wrote:
> >
> >> On Fri, Jun 26, 2009 at 4:57 PM, erik quanstrom<quanstro@quanstro.net> wrote:
> >> >> > > The script runs at boot, the echo tells me that much, but the time is not set, perhaps as if timesync -r is not working. To be specific the date a few minutes after booting is Sun Jan  2 18:30:36 GMT 2000.
> >> >> >
> >> >> > i believe timesync is setting the system clock from /dev/rtc, not the other way
> >> >> > around.
> >> >>
> >> >> Yeah, that's what I expect timesync to do, but it's doing something strange instead.
> >> >
> >> > i wouldn't classify doing what the man page says it does
> >> > as something "really strange".  if you want the converse,
> >> > then just execute "date -n >/dev/rtc".
> >> >
> >> > - erik
> >> >
> >> >
> >>
> >> I'm pretty sure he's *trying* to get the time from /dev/rtc, not
> >> trying to set it.
> >>
> >
> > You'd be right.
> >
> > I've found I don't seem to need timesync, the system time & /dev/rtc alike seem to stay in sync with the host without it, but I'm still curious why timesync -r should mess up the system time so badly.
> >
> > Perhaps /dev/rtc and the system time are linked on some architectures, so that setting one sets the other and so timesync -r gets in a mess. Just a guess.
> >
> > --
> > Ethan Grammatikidis
> > The lyf so short, the craft so long to lerne. -- Chaucer
> >
> >
> 
> 
> 
> -- 
> Federico G. Benavento
> 


-- 
Ethan Grammatikidis
The lyf so short, the craft so long to lerne. -- Chaucer

Re: [9fans] timesync -r not working?

[Federico G. Benavento]

yeah, I must read the whole thread before posting ;P

On Sat, Jun 27, 2009 at 3:02 PM, Ethan Grammatikidis<eekee57@fastmail.fm> wrote:
> On Sat, 27 Jun 2009 05:36:55 -0300
> "Federico G. Benavento" <benavento@gmail.com> wrote:
>
>> timezones?
>
> I've never heard of a timezone that could make a 9 year difference. Maybe on Pluto. ;)
>
>>
>> On Sat, Jun 27, 2009 at 4:46 AM, Ethan Grammatikidis<eekee57@fastmail.fm> wrote:
>> > On Fri, 26 Jun 2009 17:39:12 -0700
>> > John Floren <slawmaster@gmail.com> wrote:
>> >
>> >> On Fri, Jun 26, 2009 at 4:57 PM, erik quanstrom<quanstro@quanstro.net> wrote:
>> >> >> > > The script runs at boot, the echo tells me that much, but the time is not set, perhaps as if timesync -r is not working. To be specific the date a few minutes after booting is Sun Jan  2 18:30:36 GMT 2000.
>> >> >> >
>> >> >> > i believe timesync is setting the system clock from /dev/rtc, not the other way
>> >> >> > around.
>> >> >>
>> >> >> Yeah, that's what I expect timesync to do, but it's doing something strange instead.
>> >> >
>> >> > i wouldn't classify doing what the man page says it does
>> >> > as something "really strange".  if you want the converse,
>> >> > then just execute "date -n >/dev/rtc".
>> >> >
>> >> > - erik
>> >> >
>> >> >
>> >>
>> >> I'm pretty sure he's *trying* to get the time from /dev/rtc, not
>> >> trying to set it.
>> >>
>> >
>> > You'd be right.
>> >
>> > I've found I don't seem to need timesync, the system time & /dev/rtc alike seem to stay in sync with the host without it, but I'm still curious why timesync -r should mess up the system time so badly.
>> >
>> > Perhaps /dev/rtc and the system time are linked on some architectures, so that setting one sets the other and so timesync -r gets in a mess. Just a guess.
>> >
>> > --
>> > Ethan Grammatikidis
>> > The lyf so short, the craft so long to lerne. -- Chaucer
>> >
>> >
>>
>>
>>
>> --
>> Federico G. Benavento
>>
>
>
> --
> Ethan Grammatikidis
> The lyf so short, the craft so long to lerne. -- Chaucer
>
>



-- 
Federico G. Benavento

Re: [9fans] timesync -r not working?

[cinap_lenrek]

[-- Attachment #1: Type: text/plain, Size: 69 bytes --]

sure... thats why its called plan9 from outer space :)

--
cinap

[-- Attachment #2: Type: message/rfc822, Size: 4861 bytes --]

From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: 9fans@9fans.net
Subject: Re: [9fans] timesync -r not working?
Date: Sat, 27 Jun 2009 19:02:35 +0100
Message-ID: <20090627190235.781c2441.eekee57@fastmail.fm>

On Sat, 27 Jun 2009 05:36:55 -0300
"Federico G. Benavento" <benavento@gmail.com> wrote:

> timezones?

I've never heard of a timezone that could make a 9 year difference. Maybe on Pluto. ;)

> 
> On Sat, Jun 27, 2009 at 4:46 AM, Ethan Grammatikidis<eekee57@fastmail.fm> wrote:
> > On Fri, 26 Jun 2009 17:39:12 -0700
> > John Floren <slawmaster@gmail.com> wrote:
> >
> >> On Fri, Jun 26, 2009 at 4:57 PM, erik quanstrom<quanstro@quanstro.net> wrote:
> >> >> > > The script runs at boot, the echo tells me that much, but the time is not set, perhaps as if timesync -r is not working. To be specific the date a few minutes after booting is Sun Jan  2 18:30:36 GMT 2000.
> >> >> >
> >> >> > i believe timesync is setting the system clock from /dev/rtc, not the other way
> >> >> > around.
> >> >>
> >> >> Yeah, that's what I expect timesync to do, but it's doing something strange instead.
> >> >
> >> > i wouldn't classify doing what the man page says it does
> >> > as something "really strange".  if you want the converse,
> >> > then just execute "date -n >/dev/rtc".
> >> >
> >> > - erik
> >> >
> >> >
> >>
> >> I'm pretty sure he's *trying* to get the time from /dev/rtc, not
> >> trying to set it.
> >>
> >
> > You'd be right.
> >
> > I've found I don't seem to need timesync, the system time & /dev/rtc alike seem to stay in sync with the host without it, but I'm still curious why timesync -r should mess up the system time so badly.
> >
> > Perhaps /dev/rtc and the system time are linked on some architectures, so that setting one sets the other and so timesync -r gets in a mess. Just a guess.
> >
> > --
> > Ethan Grammatikidis
> > The lyf so short, the craft so long to lerne. -- Chaucer
> >
> >
> 
> 
> 
> -- 
> Federico G. Benavento
> 


-- 
Ethan Grammatikidis
The lyf so short, the craft so long to lerne. -- Chaucer

Re: [9fans] timesync -r not working?

[Ethan Grammatikidis]

On Sun, 28 Jun 2009 02:17:13 +0200
cinap_lenrek@gmx.de wrote:

> sure... thats why its called plan9 from outer space :)

*grin*

>
> --
> cinap
>


--
Ethan Grammatikidis
The lyf so short, the craft so long to lerne. -- Chaucer

Re: [9fans] timesync -r not working?

[Ethan Grammatikidis]

On Sat, 27 Jun 2009 21:05:37 -0300
"Federico G. Benavento" <benavento@gmail.com> wrote:

> yeah, I must read the whole thread before posting ;P

Hey, not reading the whole thread is my trick.

> 
> On Sat, Jun 27, 2009 at 3:02 PM, Ethan Grammatikidis<eekee57@fastmail.fm> wrote:
> > On Sat, 27 Jun 2009 05:36:55 -0300
> > "Federico G. Benavento" <benavento@gmail.com> wrote:
> >
> >> timezones?
> >
> > I've never heard of a timezone that could make a 9 year difference. Maybe on Pluto. ;)
> >
> >>
> >> On Sat, Jun 27, 2009 at 4:46 AM, Ethan Grammatikidis<eekee57@fastmail.fm> wrote:
> >> > On Fri, 26 Jun 2009 17:39:12 -0700
> >> > John Floren <slawmaster@gmail.com> wrote:
> >> >
> >> >> On Fri, Jun 26, 2009 at 4:57 PM, erik quanstrom<quanstro@quanstro.net> wrote:
> >> >> >> > > The script runs at boot, the echo tells me that much, but the time is not set, perhaps as if timesync -r is not working. To be specific the date a few minutes after booting is Sun Jan  2 18:30:36 GMT 2000.
> >> >> >> >
> >> >> >> > i believe timesync is setting the system clock from /dev/rtc, not the other way
> >> >> >> > around.
> >> >> >>
> >> >> >> Yeah, that's what I expect timesync to do, but it's doing something strange instead.
> >> >> >
> >> >> > i wouldn't classify doing what the man page says it does
> >> >> > as something "really strange".  if you want the converse,
> >> >> > then just execute "date -n >/dev/rtc".
> >> >> >
> >> >> > - erik
> >> >> >
> >> >> >
> >> >>
> >> >> I'm pretty sure he's *trying* to get the time from /dev/rtc, not
> >> >> trying to set it.
> >> >>
> >> >
> >> > You'd be right.
> >> >
> >> > I've found I don't seem to need timesync, the system time & /dev/rtc alike seem to stay in sync with the host without it, but I'm still curious why timesync -r should mess up the system time so badly.
> >> >
> >> > Perhaps /dev/rtc and the system time are linked on some architectures, so that setting one sets the other and so timesync -r gets in a mess. Just a guess.
> >> >
> >> > --
> >> > Ethan Grammatikidis
> >> > The lyf so short, the craft so long to lerne. -- Chaucer
> >> >
> >> >
> >>
> >>
> >>
> >> --
> >> Federico G. Benavento
> >>
> >
> >
> > --
> > Ethan Grammatikidis
> > The lyf so short, the craft so long to lerne. -- Chaucer
> >
> >
> 
> 
> 
> -- 
> Federico G. Benavento
> 


-- 
Ethan Grammatikidis
The lyf so short, the craft so long to lerne. -- Chaucer

Re: [9fans] timesync -r not working?

[Balwinder S Dheeman]

On 06/27/2009 12:16 AM, Ethan Grammatikidis wrote:
> I'm running plan 9 in qemu, I want to use the qemu-emulated hardware clock for the plan 9 time because it keeps the same time as the host.
>
> I made a script to be sourced from cpurc:
>
> 	#!/bin/rc
>
> 	echo '> starting timesync'
>
> 	if (! test -e '/dev/rtc')
> 		bind -a '#r' /dev
> 	aux/timesync -r
>
> The script runs at boot, the echo tells me that much, but the time is not set, perhaps as if timesync -r is not working. To be specific the date a few minutes after booting is Sun Jan  2 18:30:36 GMT 2000.
>
> Should I not use timesync at all? I ask because $boottime (which is set before timesync is started) contains a reasonable date.


I also run Plan 9 in qemu, the:

	aux/timesync -n pool.ntp.org

solved a similar problem here.

Hope that helps,
--
Balwinder S "bdheeman" Dheeman        Registered Linux User: #229709
Anu'z Linux@HOME (Unix Shoppe)        Machines: #168573, 170593, 259192
Chandigarh, UT, 160062, India         Plan9, T2, Arch/Debian/FreeBSD/XP
Home: http://werc.homelinux.net/      Visit: http://counter.li.org/

Re: [9fans] timesync -r not working?

[Ethan Grammatikidis]

On Mon, 29 Jun 2009 09:31:51 GMT
Balwinder S Dheeman <bsd.SANSPAM@cto.homelinux.net> wrote:

> On 06/27/2009 12:16 AM, Ethan Grammatikidis wrote:
> > I'm running plan 9 in qemu, I want to use the qemu-emulated hardware clock for the plan 9 time because it keeps the same time as the host.
> >
> > I made a script to be sourced from cpurc:
> >
> > 	#!/bin/rc
> >
> > 	echo '> starting timesync'
> >
> > 	if (! test -e '/dev/rtc')
> > 		bind -a '#r' /dev
> > 	aux/timesync -r
> >
> > The script runs at boot, the echo tells me that much, but the time is not set, perhaps as if timesync -r is not working. To be specific the date a few minutes after booting is Sun Jan  2 18:30:36 GMT 2000.
> >
> > Should I not use timesync at all? I ask because $boottime (which is set before timesync is started) contains a reasonable date.
>
>
> I also run Plan 9 in qemu, the:
>
> 	aux/timesync -n pool.ntp.org
>
> solved a similar problem here.

ty. That's what was in my cpurc, I don't know whether as a default or from tinkering with it a few years ago. I didn't want to load ntp.org with multiple requests from the same machine.


--
Ethan Grammatikidis
The lyf so short, the craft so long to lerne. -- Chaucer

Re: [9fans] timesync -r not working?

[erik quanstrom]

> ty. That's what was in my cpurc, I don't know whether as a default or from tinkering with it a few years ago. I didn't want to load ntp.org with multiple requests from the same machine.

running multiple timesyncs under the same kernel is an error
and will result in unpredictable behavior.

- erik

Re: [9fans] timesync -r not working?

[Steve Kostecke]

On 2009-06-29, Ethan Grammatikidis <eekee57@fastmail.fm> wrote:

> Balwinder S Dheeman <bsd.SANSPAM@cto.homelinux.net> wrote:
>
>> I also run Plan 9 in qemu, the:
>>
>>  aux/timesync -n pool.ntp.org
>>
>> solved a similar problem here.
>
> ty. That's what was in my cpurc, I don't know whether as a default or
> from tinkering with it a few years ago. I didn't want to load ntp.org
> with multiple requests from the same machine.

pool.ntp.org resolves to a random selection from over 1700 public time
servers located around the world.

You may be better off using a time server located in your geographic
area. Please see http://www.pool.ntp.org/ for a list of pool zones (and
more infomation about the pool).

--
Steve Kostecke <steve@kostecke.net>
"I am a citizen, not a consumer. I am a human being, not a revenue source."
Public Key at gopher://kostecke.net or `finger steve@kostecke.net`