9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: tlaronde@polynum.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Date woes
Date: Tue, 23 Apr 2013 18:16:01 +0200	[thread overview]
Message-ID: <20130423161601.GA485@polynum.com> (raw)
In-Reply-To: <8c612145eec4c188b76e8740293d345b@coraid.com>

On Tue, Apr 23, 2013 at 11:16:37AM -0400, erik quanstrom wrote:
> > But this may affect the way the date is displayed, not the UTC?
>
> are you sure it's not a display issue?  sometimes a double-timezone
> conversion or incorrect timezone conversion can screw up the date.
> fossil uses time(0), which in theory should not conflict.
>

But it is incorrectly setting rtc on exit to the wrong value. So this is
not a display problem. One "time" has the wrong value, /dev/rtc has the
right (until reboot, because wrong is stored---I verified in the BIOS),
and fileserver /dev/time has the wrong.

> > >
> > > 3.  i think timesync(8) may have the information you're looking for.
> > >
> >
> > Thanks for the tip. I have added it to my profile.
>
> make sure you don't have two timesyncs running!  there
> may be one in /rc/bin/termrc or /rc/bin/cpurc.  two at war
> can be a fatal problem.

I will revue all the scripts till my profile to try to understand what's
going on.

Thanks for the advices!
--
        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
                      http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C



  reply	other threads:[~2013-04-23 16:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-23 13:30 tlaronde
2013-04-23 13:34 ` erik quanstrom
2013-04-23 14:34   ` tlaronde
2013-04-23 15:16     ` erik quanstrom
2013-04-23 16:16       ` tlaronde [this message]
2013-04-23 16:59         ` erik quanstrom
2013-04-23 17:36           ` tlaronde
2013-04-23 21:55 ` Bakul Shah
2013-04-24 10:52   ` tlaronde
2013-04-24 11:26     ` tlaronde

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130423161601.GA485@polynum.com \
    --to=tlaronde@polynum.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).