For whatever reason the top reply of the Welcome to the Shadows forum (topic Living in the Shadows OOC, in case it matters) isn't responding as having been read. I open it up, read the new post. Then click the link at the bottom of the page to go back to the main section and it still registers as unread. I checked several times, and even clicking on the "Mark all posts as read" button doesn't work. I also made sure that there wasn't a new post that had been made.
I realize it isn't a big error, but I figured you might want to know about it anyway. If it doesn't matter just ignore this.
Been happening to me to.
I find that shutting down all the browser windows and deleting content files clears it up for about 5 minutes.
It has something to do with the floating time issue. Sometimes posts I make will later appear as unread by myself becasue the post time is 10 or so minutes ahead of the system (or cookie) time.
The floating time problem is related to the way that the site is currently running -- in a virtual machine. The emulated system clock in the virtual machine is unreliable at best. This problem should take care of itself when the new server goes in. (Soon, the second hard drive came in yesterdan and I'm working on OS install/configuration.)
Sweet, that's the fun part to me.
Completely OT: Sorry pH
Yeah, the fresh install and the shiny, virgin territory of an uncluttered harddrive. Ahhh...
Looking forward to the new server.
| QUOTE (Neuron Basher) |
| The floating time problem is related to the way that the site is currently running -- in a virtual machine. The emulated system clock in the virtual machine is unreliable at best. This problem should take care of itself when the new server goes in. (Soon, the second hard drive came in yesterdan and I'm working on OS install/configuration.) |
It's not that odd of a way to run a server when the original linux based host dies and all you have available is a Windows server. It's a "make it work now" kind of solution to the problem.
Hell, it's not the weirdest solution I've come up with in the 13 years I've been doing Unix administration. ![]()
ok. it actually seems fixed right now. And like I said obviously it isn't a big issue. Thanks for responding though.
It's not really fixed. What happens is that the server synchronizes itself with an NTP server every hour to fix however many minutes it's skewed from "real" time in the intervening 60 minutes. Rest assured it'll be screwed up again in a little while.
Yeah, this is getting kind of funny. I made a post and it showed up as having posted at 5:25. I then made another post a few minutes later and it came through as having posted at 5:22... 3 minutes before the previous post.
It's been happening to me for weeks. The best part is when an edit on a post is time-stamped up to 7 minutes before the actual post was made.
It's magic, I tell you! Magic!
Powered by Invision Power Board (http://www.invisionboard.com)
© Invision Power Services (http://www.invisionpower.com)