Posted: Fri 29 May 2009, 10:19 Post subject:
Psync Time Synchroniser Version 2.9 & 2.7-64bitSubject description: A small app to synchronise your PC time to a time server

Version 2.9
New version of hwclock meant the time was set incorrectly in new versions of Puppy if Psync was run first.
Norm Pierce wrote a small patch to cure this so I've added his version here.

Version 2.8

Added conditional check to the autostart to check whether wifi is in use.
Checks for wifi or wired, waits for wifi to 'up' then runs autostart if so selected.

====================

Version 2.7 Bug fix

Thanks to Burunduk.

Bugfix for change in clock file I missed when testing.

=====================

Version 2.6-64

Only for 64bit Puppys.

Compiled the used ntpdate in 64bit as well as the app. Works ok in Fatdog 64

============================

Version 2.6

I'm hoping this will once and for all trap the text errors in the final offset time report window when the server text changes length.

This means no interim releases when server text changes length.

(Sorry if it came a bit quick after 2.4. It's just this issue has annoyed me long enough.)

Version 2.5

Added DST dates display when time changes apply, if applicable to timezone.

Small change in code, it now recognises if there is no DST applicable.

==============================

Posted notes:-

You need to set your Timezone geographically for DST to work. i.e Europe/London - Europe/Madrid etc to match your nearest location to allow DST to apply to the time clock.

Scroll through the Puppy menu Desktop/Timezone list to set it to nearest location.

If you use GMT offset, Psync will still work but without DST changes. (You must reboot to make setting take)

Psync now checks from the internet which region servers are currently 'active' to set the time and uses those. This ensures a constant pool of servers, so no user intervention is required
.

======

And I thought it was a joke

Quote:

----- Time and time zones on Mars -----

Some people have adjusted their work schedules to fit Mars time.
Dozens of special Mars watches were built for Jet Propulsion
Laboratory workers who kept Mars time during the Mars Exploration
Rovers mission (2004). These timepieces look like normal Seikos and
Citizens but use Mars seconds rather than terrestrial seconds.

A Mars solar day is called a "sol" and has a mean period equal to
about 24 hours 39 minutes 35.244 seconds in terrestrial time. It is
divided into a conventional 24-hour clock, so each Mars second equals
about 1.02749125 terrestrial seconds.

The prime meridian of Mars goes through the center of the crater
Airy-0, named in honor of the British astronomer who built the
Greenwich telescope that defines Earth's prime meridian. Mean solar
time on the Mars prime meridian is called Mars Coordinated Time (MTC).

Each landed mission on Mars has adopted a different reference for
solar time keeping, so there is no real standard for Mars time zones.
For example, the Mars Exploration Rover project (2004) defined two
time zones "Local Solar Time A" and "Local Solar Time B" for its two
missions, each zone designed so that its time equals local true solar
time at approximately the middle of the nominal mission. Such a "time
zone" is not particularly suited for any application other than the
mission itself.

Many calendars have been proposed for Mars, but none have achieved
wide acceptance. Astronomers often use Mars Sol Date (MSD) which is a
sequential count of Mars solar days elapsed since about 1873-12-29
12:00 GMT.

Timezone reads GMT+0 (London etc)...
[Our timezone is London etc, but clocks here and now are set forward 1hr for summertime]
Day, date, time all correct.
Run Psync...
"NTP Time Server Synchronizer" shows the time as it is on my clock and GMT -0.3 seconds.
[Is this the amount my clock differs from the server time or what?]
Hit the synchronize button...
It moves the time back by 1 hour exactly.
The ntptime command makes no correction!
So I manually reset it forward 1 hour.

The offset shown is the time difference between the 'motherboard' hardware clock, also known as RTC (Real Time Clock) and the 'system' clock.
RTC is kept going by a small battery when PC is powered off. Also known as CMOS battery.

The 'system' clock is set by the Puppy kernel on bootup and is then kept running by software.

Depending on accuracy of the software 'ticks' the system clock will drift from the RTC clock time. Especially if system is not powered down for some time.

Psync reads your RTC and your 'system clocks' and shows the difference, usually a fraction of a second, unless you have never synchronised it before.

Psync will read the clocks and then when clicked will synchronise all clocks to a public time server.

If the display blanks, just move your mouse etc.

Psync uses NTP servers to obtain a network server time. I'm working on an update to provide a list of servers around the world so choice can be made nearer to your location.

Depending on location of server, ISP connection speed, your PC, etc then your time will always be out by a few milliseconds or so to 'atomic time'.

That is known as 'time' latency.

Rob_________________Rob
-
The moment after you press "Post" is the moment you actually see the typso Last edited by tasmod on Tue 18 Oct 2011, 05:22; edited 2 times in total

1. "You must set your Timezone geographically"
OK, it's now set to "London" and all is looking good.
My little travel clock here is only 6 seconds slower [not bad eh?]
That because it took my wife 6 seconds delay to set it when the TV clock changed to the next minute.
Hence I have [imprecise] confirmation that Psync is setting the time correctly.

2. "Use %T for hrs min secs in 24hr format"
That did the trick!
How easy is that?
When you know how that is.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum