for a good time, set your clock to 2^32+1 seconds since the epoch

Bug #313619 reported by Zooko Wilcox-O'Hearn
4
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:~/.tahoe-testgrid$ time sudo updatedb
Password:
/usr/bin/find: /system/contract/process/128084: Value too large for defined data type
/usr/bin/find: /system/contract/all/128084: Value too large for defined data type

real 7m39.507s
user 0m10.394s
sys 0m17.228s
 nooxie:~/.tahoe-testgrid$

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.

Revision history for this message
Tim Spriggs (tim-tajinc) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.