From: Brian D. <bda...@gm...> - 2007-03-25 02:37:24
|
Does anyone know why the timestamps on files always are Dec 31, 1969 (I'm sure it's that they are they all 0, and time is measured in seconds since Jan 1, 1970)? Or, what I really care about -- how can I get it to record the timestamp when the file was actually created (assuming I've set my system clock correctly). I'm running ext2 on a 3 GB microdrive, so I'm not concerned about limiting the number of writes to the media. I've got compilers working on the gumstix, but I can't get make to compile. Even if make would compile, it wouldn't function properly, since it relies on timestamps in the filesystem. Thanks, Brian |
From: <ro...@in...> - 2007-03-26 15:52:48
|
Quoting Brian Davidson <bda...@gm...>: > Does anyone know why the timestamps on files always are Dec 31, 1969 > (I'm sure it's that they are they all 0, and time is measured in > seconds since Jan 1, 1970)? Or, what I really care about -- how can > I get it to record the timestamp when the file was actually created > (assuming I've set my system clock correctly). I believe the solution is to run ntpd (network time protocol daemon) on the gumstix. ntpd queries a time server and updates the local clock. I think clients are typically configured to reference time servers at ntp.org or other external servers, but I think it's also possible to run a time server locally in case an external time server is not accessible from the gumstix. ntp can be selected (via make menuconfig) as a package to compile for the gumstix -- it appears to be disabled by default. I don't know much about this, so if you get it figured out, I would be interested to hear about how you made it work. Hope this helps, Robert Dodier |
From: Brian D. <bda...@gm...> - 2007-03-26 20:32:08
|
On Mar 26, 2007, at 11:52 AM, ro...@in... wrote: > Quoting Brian Davidson <bda...@gm...>: > > I believe the solution is to run ntpd (network time protocol daemon) > on the gumstix. ntpd queries a time server and updates the local > clock. > I think clients are typically configured to reference time servers > at ntp.org or other external servers, but I think it's also possible > to run a time server locally in case an external time server is not > accessible from the gumstix. NTP will do a good job of getting the system time set correctly. The problem I'm having is that even with system time set correctly, new files are created with a timestamp of 0, which equates to Dec 31, 1969 23:59:59. It's something with the filesystem in general that's not storing timestamps, as it happens with both jffs2 and ext2 filesystems. I was hoping someone knew off the top of their head. Since it doesn't sound like it, I'll dig into the source code and patches and see if I can't figure it out. Brian |
From: <ro...@in...> - 2007-03-26 21:03:37
|
Quoting Brian Davidson <bda...@gm...>: > NTP will do a good job of getting the system time set correctly. The > problem I'm having is that even with system time set correctly, new > files are created with a timestamp of 0, which equates to Dec 31, > 1969 23:59:59. It's something with the filesystem in general that's > not storing timestamps, as it happens with both jffs2 and ext2 > filesystems. Brian, I do not see that behavior. After using NTP to set the system clock, I find that cat > /tmp/foo.out and cat > /etc/bar.out (to test writing to volatile and nonvolatile parts of the filesystem) I find those files have the current date & time, not Jan 1, 1970. Maybe I am misunderstanding what is the problem. For the record I tried the above operations w/ buildroot = r1161. best Robert Dodier |
From: Grahame J. <gb...@th...> - 2007-03-27 11:58:11
|
Hi, ntp is OK if you have a connection to the net. I am connected point-to-point with the host machine on usb0 or bnep0 The way that I go around it was to push the time/date over http as the client program connects. A bit of c code for a cgi that essentially does settimeofday(&time, &timez); I would like a better solution. Maybe run rdate as it boots. I am not sure if this runs on a Windows box? Cheers Grahame Jordan ro...@in... wrote: > Quoting Brian Davidson <bda...@gm...>: > > >> NTP will do a good job of getting the system time set correctly. The >> problem I'm having is that even with system time set correctly, new >> files are created with a timestamp of 0, which equates to Dec 31, >> 1969 23:59:59. It's something with the filesystem in general that's >> not storing timestamps, as it happens with both jffs2 and ext2 >> filesystems. >> > > Brian, I do not see that behavior. After using NTP to set the > system clock, I find that > cat > /tmp/foo.out > and > cat > /etc/bar.out > (to test writing to volatile and nonvolatile parts of the filesystem) > I find those files have the current date & time, not Jan 1, 1970. > Maybe I am misunderstanding what is the problem. > > For the record I tried the above operations w/ buildroot = r1161. > > best > Robert Dodier > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > |
From: Brian D. <bda...@gm...> - 2007-03-27 06:32:07
|
On Mar 26, 2007, at 5:03 PM, ro...@in... wrote: > Brian, I do not see that behavior. After using NTP to set the > system clock, I find that > cat > /tmp/foo.out > and > cat > /etc/bar.out > (to test writing to volatile and nonvolatile parts of the filesystem) > I find those files have the current date & time, not Jan 1, 1970. > Maybe I am misunderstanding what is the problem. You understand the problem. > For the record I tried the above operations w/ buildroot = r1161. Very helpful! I see what you see with r1093, however I tried with r1329 and r1346 I got the behavior I described. I didn't try writing to /tmp with these... Here's an interesting one on r1223: # cd /tmp # while [ 1 ] > do > touch foo ; ls -al foo > done -rw-r--r-- 1 root root 0 Jun 29 1979 foo -rw-r--r-- 1 root root 0 Aug 4 1980 foo -rw-r--r-- 1 root root 0 Sep 15 1981 foo -rw-r--r-- 1 root root 0 Oct 26 1982 foo -rw-r--r-- 1 root root 0 Dec 2 1983 foo -rw-r--r-- 1 root root 0 Jan 13 1985 foo -rw-r--r-- 1 root root 0 Feb 22 1986 foo -rw-r--r-- 1 root root 0 Apr 1 1987 foo -rw-r--r-- 1 root root 0 May 12 1988 foo -rw-r--r-- 1 root root 0 Jun 23 1989 foo -rw-r--r-- 1 root root 0 Jul 30 1990 foo -rw-r--r-- 1 root root 0 Sep 6 1991 foo -rw-r--r-- 1 root root 0 Oct 20 1992 foo -rw-r--r-- 1 root root 0 Dec 3 1993 foo -rw-r--r-- 1 root root 0 Jan 12 1995 foo -rw-r--r-- 1 root root 0 Feb 28 1996 foo -rw-r--r-- 1 root root 0 Apr 5 1997 foo -rw-r--r-- 1 root root 0 May 12 1998 foo -rw-r--r-- 1 root root 0 Jun 30 1999 foo -rw-r--r-- 1 root root 0 Aug 4 2000 foo -rw-r--r-- 1 root root 0 Jan 3 1970 foo -rw-r--r-- 1 root root 0 Feb 15 1971 foo -rw-r--r-- 1 root root 0 Mar 23 1972 foo -rw-r--r-- 1 root root 0 Apr 29 1973 foo -rw-r--r-- 1 root root 0 Jun 15 1974 foo -rw-r--r-- 1 root root 0 Jul 21 1975 foo -rw-r--r-- 1 root root 0 Aug 26 1976 foo -rw-r--r-- 1 root root 0 Oct 9 1977 foo -rw-r--r-- 1 root root 0 Nov 15 1978 foo -rw-r--r-- 1 root root 0 Dec 22 1979 foo -rw-r--r-- 1 root root 0 Feb 5 1981 foo -rw-r--r-- 1 root root 0 Mar 13 1982 foo -rw-r--r-- 1 root root 0 Apr 19 1983 foo -rw-r--r-- 1 root root 0 Jun 2 1984 foo -rw-r--r-- 1 root root 0 Jul 8 1985 foo -rw-r--r-- 1 root root 0 Aug 14 1986 foo -rw-r--r-- 1 root root 0 Sep 30 1987 foo -rw-r--r-- 1 root root 0 Nov 5 1988 foo -rw-r--r-- 1 root root 0 Dec 11 1989 foo -rw-r--r-- 1 root root 0 Jan 26 1991 foo -rw-r--r-- 1 root root 0 Mar 3 1992 foo -rw-r--r-- 1 root root 0 Apr 9 1993 foo -rw-r--r-- 1 root root 0 May 25 1994 foo -rw-r--r-- 1 root root 0 Jul 1 1995 foo -rw-r--r-- 1 root root 0 Aug 6 1996 foo -rw-r--r-- 1 root root 0 Sep 21 1997 foo -rw-r--r-- 1 root root 0 Oct 26 1998 foo -rw-r--r-- 1 root root 0 Dec 4 1999 foo -rw-r--r-- 1 root root 0 Jan 8 2001 foo -rw-r--r-- 1 root root 0 Jun 12 1970 foo -rw-r--r-- 1 root root 0 Jul 18 1971 foo I'm guessing that's endian related... I'm trying to figure out where it broke. Unfortunately, buildroots take a long time to build. It works in r1184. I'll poke away at it again tomorrow. It's getting a bit late... Brian |
From: Brian D. <bda...@gm...> - 2007-03-28 00:47:30
|
It looks like this problem started in buildroot r1185. Can someone else confirm this for a buildroot >= r1185? If you have a newer one, and timestamps work, could you please let me know what version you're running? Thanks! Brian On Mar 27, 2007, at 2:32 AM, Brian Davidson wrote: > # cd /tmp > # while [ 1 ] >> do >> touch foo ; ls -al foo >> done > -rw-r--r-- 1 root root 0 Jun 29 1979 foo > -rw-r--r-- 1 root root 0 Aug 4 1980 foo > -rw-r--r-- 1 root root 0 Sep 15 1981 foo > -rw-r--r-- 1 root root 0 Oct 26 1982 foo > -rw-r--r-- 1 root root 0 Dec 2 1983 foo > > I'm guessing that's endian related... > > I'm trying to figure out where it broke. Unfortunately, buildroots > take a long time to build. It works in r1184. I'll poke away at it > again tomorrow. It's getting a bit late... |
From: Arnar B. <ar...@gm...> - 2007-03-28 20:37:20
|
On 3/28/07, Brian Davidson <bda...@gm...> wrote: > It looks like this problem started in buildroot r1185. Can someone > else confirm this for a buildroot >= r1185? If you have a newer one, > and timestamps work, could you please let me know what version you're > running? > > On Mar 27, 2007, at 2:32 AM, Brian Davidson wrote: > > > # cd /tmp > > # while [ 1 ] > >> do > >> touch foo ; ls -al foo > >> done > > -rw-r--r-- 1 root root 0 Jun 29 1979 foo > > -rw-r--r-- 1 root root 0 Aug 4 1980 foo > > -rw-r--r-- 1 root root 0 Sep 15 1981 foo > > -rw-r--r-- 1 root root 0 Oct 26 1982 foo > > -rw-r--r-- 1 root root 0 Dec 2 1983 foo I have r1322 and I see the same problem. Arnar |