On Mittwoch, 5. April 2006 17:21 Justin Mason wrote: > no -- it's not the tag-time that matters; it's the time that the > mass-check started at, expressed in the UTC timezone. Because the > "zmi" mass-check happens *after* 0000 UTC, it shows up as being in > the next "day" period.
I used to have this type of time scheduling problem the last time I worked for a bank here in Austria: They've got lots of jobs running over night, each at a fixed time. Because nobody knew exactly which job depended on which other, they needed this. And they got problems when some jobs only finished after another, depeding job started already. For this, they had a special department searching the wrong transfers and manually booking them back... In short: I'll swap the mass_check with my backup times. So mass_check will start at 01:03 from tonight. mfg zmi -- // Michael Monnerie, Ing.BSc --- it-management Michael Monnerie // http://zmi.at Tel: 0660/4156531 Linux 2.6.11 // PGP Key: "lynx -source http://zmi.at/zmi2.asc | gpg --import" // Fingerprint: EB93 ED8A 1DCD BB6C F952 F7F4 3911 B933 7054 5879 // Keyserver: www.keyserver.net Key-ID: 0x70545879
pgpYpaWpxEZP3.pgp
Description: PGP signature
