From what I gathered in the documentations on both sides of the
fence, Unix traditionally stamps file times (create/status change,
modify and last read access) with a long integer (32 bits) counting
full seconds since midnight A.M. January 1, 1970 in Greenwhich, EU,
whereas the NT File
From what I gathered in the documentations on both sides of the
fence, Unix traditionally stamps file times (create/status change,
modify and last read access) with a long integer (32 bits) counting
full seconds since midnight A.M. January 1, 1970 in Greenwhich, EU,
whereas the NT File
Dragan Krnic wrote:
From what I gathered in the documentations on both sides of the
fence, Unix traditionally stamps file times (create/status change,
modify and last read access) with a long integer (32 bits) counting
full seconds since midnight A.M. January 1, 1970 in Greenwhich, EU,
On Sat, Nov 05, 2005 at 02:32:27AM +0100, Thomas Bork wrote:
Dragan Krnic wrote:
From what I gathered in the documentations on both sides of the
fence, Unix traditionally stamps file times (create/status change,
modify and last read access) with a long integer (32 bits) counting
full
When the Central European Time was last switched back to standard,
at 03:00 last Sunday, the October 30th, a process died on one of my
Windows clients with a mysterious unknown error. When it was
restarted it just went merrily on with its task. Luckily it wasn't
part of a life support system.
I
