9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Gregory Pavelcak <g.pavelcak@comcast.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Strange date/time on some created files
Date: Sat, 11 Feb 2006 10:28:13 -0500	[thread overview]
Message-ID: <82da10e4ade94db9e78b822921d9c951@comcast.net> (raw)
In-Reply-To: <6e1e1864e6c9a4ada8f05e89a676076f@collyer.net>

> That would be my web page (for fs64), but fs64 is a ken fs, so you
> couldn't have run the commands you showed on it.  I'm puzzled.

Right. The commands for my little test were run from drawterm.

> 
> It does sound like a time-zone problem.  If it's really an fs64 file
> server, what does "date" print, as Russ suggested, and what is
> conf.minuteswest set to (usually in /sys/src/fs/<fileserver>/9*.c)?

This morning, the output of 'date' from drawterm:

Sat Feb 11 10:00:01 EST 2006

then, after the walk downstairs to the server

Sat Feb 11 10:01:18 2006 + 0

I never set the time zone in the sources, so it reads
	conf.minuteswest = 8*60;

I recall having
some date problems when I built the fileserver, so I set
the time in the machine's bios to 8 hrs ahead of me
(I actually rebooted and double checked that),
and I'm pretty sure that, at some point I even
set the date on the file server using a seconds value.
I have the timezone set correctly on the
cpu server, so perhaps the combination of these things is
producing the strange result. Anyway, I botched it somehow.

Russ's other suggestion, 9fs boot; ls -l /n/boot, I'm
assuming I can just run at drawterm. I'm not sure what
to look for here. It produced this:

d-rwxrwxr-x M 93 sys    sys     0 Dec  6 07:55 /n/boot/386
d-rwxrwxr-x M 93 sys    sys     0 Dec  6 07:55 /n/boot/68000
d-rwxrwxr-x M 93 sys    sys     0 Dec  6 07:55 /n/boot/68020
--r--r--r-- M 93 sys    sys 13006 Jul 13  2005 /n/boot/LICENSE
--rw-rw-r-- M 93 sys    sys 14333 Jun 28  2003 /n/boot/LICENSE.afpl
--rw-rw-r-- M 93 sys    sys 15081 Jun 25  2003 /n/boot/LICENSE.gpl
--r--r--r-- M 93 sys    sys    63 Apr 14  2002 /n/boot/NOTICE
d-rwxrwxr-x M 93 sys    sys     0 Dec  6 07:56 /n/boot/acme
d-rwxrwxr-x M 93 adm    adm     0 Dec  7 11:46 /n/boot/adm
d-rwxrwxr-x M 93 sys    sys     0 Dec  6 07:56 /n/boot/alpha
d-rwxrwxr-x M 93 sys    sys     0 Dec  6 08:44 /n/boot/amd64
d-rwxrwxr-x M 93 sys    sys     0 Dec  6 07:56 /n/boot/arm
d-rwxrwxrwx M 93 sys    sys     0 Dec  6 07:56 /n/boot/cron
d-r-xr-xr-x M 93 bootes adm     0 Dec  6 07:50 /n/boot/dist
d-rwxrwxr-x M 93 sys    sys     0 Dec  6 07:56 /n/boot/env
d-rwxrwxr-x M 93 sys    sys     0 Dec  6 07:56 /n/boot/fd
d-rwxrwxr-x M 93 sys    sys     0 Feb  5 14:51 /n/boot/lib
d-rwxrwxr-x M 93 sys    sys     0 Dec  6 08:04 /n/boot/lp
d-rwxrwxr-x M 93 upas   upas    0 Dec  6 08:04 /n/boot/mail
d-rwxrwxr-x M 93 sys    sys     0 Dec  6 08:05 /n/boot/mips
d-rwxrwxr-x M 93 sys    sys     0 Dec  6 08:05 /n/boot/mnt
d-rwxrwxr-x M 93 sys    sys     0 Dec  6 08:05 /n/boot/n
d-rwxrwxr-x M 93 sys    sys     0 Dec  6 08:05 /n/boot/power
d-rwxrwxr-x M 93 sys    sys     0 Dec  6 08:05 /n/boot/rc
d-rwxrwxr-x M 93 sys    sys     0 Dec  6 08:05 /n/boot/sparc
d-rwxrwxr-x M 93 sys    sys     0 Dec  6 08:44 /n/boot/sparc64
d-rwxrwxr-x M 93 sys    sys     0 Dec  6 08:14 /n/boot/sys
d-r-xr-xr-x M 93 sys    sys     0 Dec  8 11:15 /n/boot/tmp
d-rwxrwxr-x M 93 sys    sys     0 Dec  6 10:46 /n/boot/usr


I don't know at this point. I have a bit of a virus, so I'm
even more confused than usual.

Thanks though.

Greg



  reply	other threads:[~2006-02-11 15:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-10 14:50 Gregory Pavelcak
2006-02-10 16:59 ` Russ Cox
2006-02-11  1:12 ` geoff
2006-02-11 15:28   ` Gregory Pavelcak [this message]
2006-02-11 15:51     ` Russ Cox
2006-02-12  2:14       ` geoff
2006-02-12  2:26         ` Russ Cox
2006-02-12  3:10           ` Bruce Ellis
2006-02-12  3:36             ` geoff
2006-02-12  3:53               ` Bruce Ellis
2006-02-12 11:06                 ` Russ Cox

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=82da10e4ade94db9e78b822921d9c951@comcast.net \
    --to=g.pavelcak@comcast.net \
    --cc=9fans@cse.psu.edu \
    /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).