The server clock just went bungholio on us. This one's for Cid or Samuraid. <3
EDIT: Okay it already was messed up beforehand but now it's one day ahead of realtime.
The server clock just went bungholio on us. This one's for Cid or Samuraid. <3
EDIT: Okay it already was messed up beforehand but now it's one day ahead of realtime.
Bow before the mighty Javoo!
Yay, Ciddies results!Guess you'll just have to post them now.
Wat
is
going
on
wtf
rawr
Now that would have been a cunning plan.
Bow before the mighty Javoo!
The clock was again completely off after the power at the datacenter failed again. The hardware clock was actually correct, but the system clock was not. It's updated now, but vBulletin has this strange habit of ordering posts by database date instead of ID.
EDIT: Gah, it's a day off. *sets* This will make forum posting interesting...
If anyone posts in this topic, their post will end up first probably.
EDIT 2: And Xander got to be the lucky poster.
... Do I win? second poster, nope.
I wish there was something we could do about it...I guess it will just have to straighten out over the next 18 hours or so...![]()
I can run SQL queries through the Admin CP. I could change the dateline on each post made while the problems were going on so that they're a more realistic time... but I don't know how many there are.Originally Posted by Samuraid
Bow before the mighty Javoo!
This clock thing is so cool you should set it to happen on Whacky Wednesday or something stupid like that.
[test]
Bow before the mighty Javoo!
Big thanks to Samuraid for working with me to save everyone a 16 hour wait before they could post again.![]()
Bow before the mighty Javoo!
Big thanks to BoB for masterminding the operation.![]()
Senior Site Staff own all of your souls.![]()
Bow before the mighty Javoo!
Whacky Wednesday has sex appeal.