From: Gregory Pavelcak <g.pavelcak@comcast.net>
To: 9fans@cse.psu.edu
Subject: [9fans] Strange date/time on some created files
Date: Fri, 10 Feb 2006 09:50:47 -0500 [thread overview]
Message-ID: <24539f67e13456dddb0efcbcf40d4bde@comcast.net> (raw)
I think something is broken somewhere in the dating
of newly created files.
I have an older style fileserver (fs64 from some generous
developer's webpage, though I don't recall who now.), and a
cpu/auth server. The commands shown are run from
drawterm on Mac OS X, in case that matters.
Output of date is correct. I also ran it from the file server
and cpu server directly and got the same result. I have no
idea why it thinks t2 was created at 12:33!
Greg
-=-=-=-=-=
cpu% date
Fri Feb 10 09:33:54 EST 2006
cpu% touch t1
cpu% >t2
cpu% ls -l t[12]
--rw-r--r-- M 11516 gp gp 0 Feb 10 09:34 t1
--rw-r--r-- M 11516 gp gp 0 Feb 10 12:33 t2
next reply other threads:[~2006-02-10 14:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-10 14:50 Gregory Pavelcak [this message]
2006-02-10 16:59 ` Russ Cox
2006-02-11 1:12 ` geoff
2006-02-11 15:28 ` Gregory Pavelcak
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=24539f67e13456dddb0efcbcf40d4bde@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).