Boost C++ Libraries: Ticket #7936: Kernel boot up time changes with host clock change https://svn.boost.org/trac10/ticket/7936 <p> With each clock changes of the host computer, obtaining <a class="missing wiki">LastBootUpTime</a> will result in a different value. Since boost interprocess relies heavily on <a class="missing wiki">LastBootUpTime</a> in windows, it's making a lot of problems in systems with time synchronization enabled. </p> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/7936 Trac 1.4.3 Ion Gaztañaga Mon, 28 Jan 2013 20:57:34 GMT <link>https://svn.boost.org/trac10/ticket/7936#comment:1 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/7936#comment:1</guid> <description> <p> If I change the date or synchronize the clock on my Windows 7, the <a class="missing wiki">LastBootUpTime</a> does not change (tested with command line "wmic os get lastbootuptime"). Only if timezone is changed the last part is modified (e.g. 20130128175525.610798+060 -&gt; 20130128105525.610798-360) </p> <p> Which system are you using? Can you add more information about the precision error? </p> </description> <category>Ticket</category> </item> <item> <author>saboorian@…</author> <pubDate>Wed, 30 Jan 2013 14:22:33 GMT</pubDate> <title/> <link>https://svn.boost.org/trac10/ticket/7936#comment:2 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/7936#comment:2</guid> <description> <p> I tested with 3 PCs one XP x86 and two 7 x86. I'm still confused about the exact reason for when it does happen and when it doesn't. One scenario is this: <br /> 1- Start windows <br /> 2- run "wmic os get lastbootuptime" <br /> 3- change time manually <br /> 4- wait for 5 to 10 minutes. (sometimes it does not change immediately. I'm not sure why. Also when I tried to find the exact timeout required for the change, the change did not happen at all. Maybe it has something to do with idle time.) <br /> 5- run "wmic os get lastbootuptime" --&gt; new result! <br /> </p> </description> <category>Ticket</category> </item> <item> <dc:creator>Ion Gaztañaga</dc:creator> <pubDate>Wed, 22 May 2013 18:43:22 GMT</pubDate> <title>status changed; resolution set https://svn.boost.org/trac10/ticket/7936#comment:3 https://svn.boost.org/trac10/ticket/7936#comment:3 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">fixed</span> </li> </ul> <p> (In <a class="changeset" href="https://svn.boost.org/trac10/changeset/84424" title="Changed bootstamp function in Windows to use EventLog service Changed ...">[84424]</a>) Changed bootstamp function in Windows to use <a class="missing wiki">EventLog</a> service start time as system bootup time. Previously used <code>LastBootupTime</code> from WMI was unstable with time synchronization and hibernation and unusable in practice. If you really need to obtain pre Boost 1.54 behaviour define <code>BOOST_INTERPROCESS_BOOTSTAMP_IS_LASTBOOTUPTIME</code> from command line or <code>detail/workaround.hpp</code>. Fixes <a class="closed ticket" href="https://svn.boost.org/trac10/ticket/7936" title="#7936: Bugs: Kernel boot up time changes with host clock change (closed: fixed)">#7936</a> </p> Ticket