for a good time, set your clock to 2^32+1 seconds since the epoch
Bug #313619 reported by
Zooko Wilcox-O'Hearn
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Nexenta Operating System |
Confirmed
|
Low
|
Unassigned |
Bug Description
I set my system clock to 2^32+1 seconds since the epoch. Pretty soon I had files with timestamps which were so large that when I ls'ed them, ls crashed.
I managed to touch them back into the present, except for these two:
nooxie:
Password:
/usr/bin/find: /system/
/usr/bin/find: /system/
real 7m39.507s
user 0m10.394s
sys 0m17.228s
nooxie:
Also along the way svc.configd died, for unknown to my reasons. A nice person named dtbartle on IRC helped me restart it and now everything is fine.
To post a comment you must log in.
http:// en.wikipedia. org/wiki/ Year_2038_ problem