9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Date woes
Date: Tue, 23 Apr 2013 09:34:46 -0400	[thread overview]
Message-ID: <0a19e826eda9d8a748239ae8b38a9cb8@brasstown.quanstro.net> (raw)
In-Reply-To: <20130423133003.GB19997@polynum.com>

> 1) How can fossil and the system display two different dates? Are they
> not using the very same system value?
>
> 2) Could it be that fossil takes CMOS and then continue on its own or
> takes CMOS constantly, while the kernel (?) takes CMOS, then leaves it
> alone, correct (wrongly) and counts in software, overwriting the value
> only when rebooting?
>
> 3) Is there something related to Windows "compatibility"? I mean,
> Windows stores (stored) local time, and is there a variable that
> instructs to correct the CMOS value?

1.  check your $timezone environment variable.  it could be they
are different for fossil and the shell.  $timezone is in /env, and there
is an independent /env for each process group, so it is entirely
possible to have many values on the same system.

3.  i think timesync(8) may have the information you're looking for.

- erik



  reply	other threads:[~2013-04-23 13:34 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 [this message]
2013-04-23 14:34   ` tlaronde
2013-04-23 15:16     ` erik quanstrom
2013-04-23 16:16       ` tlaronde
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=0a19e826eda9d8a748239ae8b38a9cb8@brasstown.quanstro.net \
    --to=quanstro@quanstro.net \
    --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).