Quote from: dzimmerm56 on May 22, 2018, 06:43:04 PM

Quote from: VRobb on May 22, 2018, 06:02:18 PM

Yeah I've seen that too, the ckpool Android app gives 2400 for midnight instead of 0000. Weird, but nothing to see here I'd guess!

Mine On! Cool

-EDIT- and you'll get false block alerts, too, after pool restarts... Tongue

I am aware of the false block found symptom after a pool restart. I also can see where 2400 would be valid for midnight depending on how you define things.
What I was a bit concerned about was that the Last Block: found time is 2018-05-21 24:08:25.

That has a time stamp of over 24 hours and is not a valid time in any system I know of on planet earth.

From John Ringo's "Troy Rising" series book one.
It is said that in science the greatest changes come about when some researcher says "Hmmm. That's odd."

I used to be a Novell Administrator long ago and in a different life. The later versions of Novell used something call eDirectory which was a database that
kept track of all the objects in the Novell network. Part of having a consistent database is a very precise tracking of time. The Novell database could be distributed across many servers and many geographic regions. Because of this the database had to know the precise time of any event so it could properly update the database with the most current changes.

A time stamp of over 24 hours would not have been allowed in Novell. I was just wondering if Kano might need clues to find out why his program seg-faulted.
It is my job as a concerned member of Kano pool to bring up little things that would not seem to make a difference when bad things are happening with no apparent cause.

Now if the android app is treating 24 = 0, then 24:08:25 could be a valid time stamp. I just never noticed it doing that before which is why I brought it up after kano pool had its issue.

The app shows 11:08 for me. So maybe there's something off in how it's add/subtracting your timezone from the original time zone.