From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: Date: Sat, 11 Feb 2006 10:51:58 -0500 From: Russ Cox To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: [9fans] Strange date/time on some created files In-Reply-To: <82da10e4ade94db9e78b822921d9c951@comcast.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <6e1e1864e6c9a4ada8f05e89a676076f@collyer.net> <82da10e4ade94db9e78b822921d9c951@comcast.net> Topicbox-Message-UUID: fbfa88f2-ead0-11e9-9d60-3106f5b1d025 > Sat Feb 11 10:00:01 EST 2006 > > then, after the walk downstairs to the server > > Sat Feb 11 10:01:18 2006 + 0 That sure looks like New York time. > I never set the time zone in the sources, so it reads > conf.minuteswest =3D 8*60; That sure looks like California time. If your file server is really in 8*60, then it thinks it's 10am in California, which explains why the files say 1pm in New York. > 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), The machine's bios should be set to GMT, which is only five hours ahead of you. Set the bios to GMT and then it doesn't matter what you've got minuteswest set to, except for what time zone the file server prints its dates in and when it thinks 5am is to run the dump. > 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: Sorry, once upon a time you could stat the root of a file server to find out what it thought the current time was. I should have tried it first, though. I meant ls -ld, but even that doesn't work, because it stats the mount point and not the root of the mounted file server. I don't think it's possible to stat the root of a mounted fil= e server anymore. Russ