Folding Forum

bruce wrote:Doesn't anybody run "timed" any more?

bruce wrote:The daemon "timed" synchronizes the clocks of networked *inux machines to one machine that's running a master clock. Microsoft had something like that for WIndows, but it doesn't seem to work any more, though you can download things like Atomic-Clock-Sync or other programs that can sync your clock with one of the government's master clocks.

gwildperson wrote:Is there a way to have NTP update more frequently? Linux in a Virtual Machine requires the AMD patch to keep reasonable time, but it still may be drifting more than the real hardware drifts.

Is there a NTP for Windows so that both can be synchronized to the same clock?

# Sync system time with NTP
0 3 * * 0 /usr/local/bin/sync-time.sh

#!/bin/bash

# Get the NTP server IP from the NTP server configuration /etc/ntp.conf
SERVER=$(grep ^server /etc/ntp.conf | awk '{print $2}' | head -1)

echo -n "Stopping ntpd ... "
/etc/init.d/ntpd stop > /dev/null 2>&1
echo    "done"

echo -n "Syncing system time with NTP ... "
/usr/sbin/ntpdate $SERVER > /dev/null 2>&1
echo    "done"

echo -n "Setting hardware clock to system time ... "
/sbin/hwclock --systohc > /dev/null 2>&1
echo    "done"

echo -n "Starting ntpd ... "
/etc/init.d/ntpd start > /dev/null 2>&1
echo    "done"

uncle_fungus wrote:Sure, the "all frames" method bases it's calculation on a set of 255 stored frames. As soon as 255 frames have been stored new frame times no longer count, which means if the spec of your machine suddenly changes, or the core suddenly becomes more efficient the data will be obsolete.
The "effective rate" method calculates the frame time based on (time now - download time) / current frame which gives a much better estimate of your PPD and frame time across the current WU.
The other methods, "last frame only" and "last 3 frames" show your instantaneous PPD, and a smoothed instantaneous PPD. This may not always accurately reflect the overall PPD you get for a particular WU.