https://bugzilla.wikimedia.org/show_bug.cgi?id=20328
Brion Vibber <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] Status|NEW |RESOLVED Resolution| |INVALID --- Comment #2 from Brion Vibber <[email protected]> 2009-08-21 00:21:15 UTC --- I'm going to take the liberty of marking this bug invalid on the basis that, well, nothing's going to work right if you're fiddling with the clock in this way. :) (Virtualization _should_ not be sending your clock backwards unless you're doing something very odd indeed, like putting all your storage on an external server so it persists, then reverting the VM state to a previous snapshot, *and* not having the clock set to synchronize properly.) A couple of likely causes of the viewed behavior off the top of my head: 1) Your session states are getting utterly corrupted by the broken time situation or 2) Login worked just fine, but your browser is telling the server it's already seen a more recent version of the page so the server quite legitimately responds with a '304 Not Modified'. Since all such caching behavior is based on having clocks set consistently, I can only recommend fixing your VM'c configuration to update its clock correctly on suspend/resume. -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
