Puppy Linux Discussion Forum

tasmod

############Please read the Help file##########

Will now handle a large offset and different date

Posted notes:-
You must set your Timezone geographically. i.e Europe/London - Europe/Madrid etc to match your nearest location.

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

NOT by GMT offset. (You must reboot to make setting take)

Previous versions now removed. This is because they contained 'hard coded' ip addresses which may 'go down'.
Checks from internet which servers are active.

This version 1.0 is a small update in the help file and display text only. Functionality is the same.
This is the final version, I assume no more updates are required.

Sylvander · Posted: Fri 29 May 2009, 12:37 Post_subject:

Installed the program OK.
It ran OK.

When I synchronized the time it set my clock forward from about 17:30 on Fri 29th May to Sat 30th May some minutes after midnight.
I'm near Edinburgh, Scotland, UK.

Have now manually reset my time to correct it.

How do I configure the prog to make it do what it aught?

My clock [in BoxPup 4.1.3] is showing 17:32 at the moment...
Any idea how I should configure it to display seconds too?

tasmod · Posted: Fri 29 May 2009, 12:57 Post_subject:

What did the timezone report ?

Sounds like you haven't set a timezone.

For seconds, change %R to %X

tasmod · Posted: Fri 29 May 2009, 13:02 Post_subject:

You will need to reboot if you change timezone to make it set.

I've posted it as Psync, it just has minor changes to the view.

Sylvander · Posted: Fri 29 May 2009, 15:10 Post_subject:

Time zone was/is set to GMT+0 = London etc.

See screenshot before using "Time synchronizer" and then after.

Setting %R to %X added seconds but changed from 24hr clock to 12hr. Sad

dawnsboy · Joined: 03 Dec 2008 Posts: 148 Location: Indiana

I downloaded and installed this program, set the time zone, rebooted and then synchronized the clock. It worked just fine. Thanks.

tlchost

Bruce B · Joined: 18 May 2005 Posts: 7421 Location: Los Angeles

Bruce B · Joined: 18 May 2005 Posts: 7421 Location: Los Angeles

Sylvander,

I can't tell by your posting. Do things show right in terms of
TZ and date+time after reboot?

If not, please detail.

Bruce

01micko · Posted: Sat 30 May 2009, 04:11 Post_subject:

Hey Rob

Nice little app!

As it turns out, my system time was only 11 seconds fast, so your Psync corrected it instantly. Thanks,

(and it seems quite compatible with Upup Wink

)

Mick

Sylvander · Posted: Sat 30 May 2009, 04:47 Post_subject:

Bruce B
Just now boot my PC.

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! Sad

So I manually reset it forward 1 hour.

tasmod · Posted: Sat 30 May 2009, 06:45 Post_subject:

OK, now I know the problem.

You must set your Timezone geographically. i.e Europe/London Europe/Madrid etc to match your nearest location.

Scroll through the list to set it to nearest location.

NOT by GMT offset.

This is because the built in commands use the locale settings.

Locale contains information on offset plus DST etc. allowing psync to set according to location.
It also allows the desktop clock to auto change for DST.

GMT file is just a numerical offset etc. which means psync ignores it and sets your clock according to server location (USA)

Rob

tasmod · Posted: Sat 30 May 2009, 07:00 Post_subject:

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.

Strangely, if the offset is different by an amount larger than say 3 minutes then the time set will blank the display for some time whilst it resets the time. It can be minutes or so before desktop returns.

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

tasmod · Posted: Sat 30 May 2009, 07:17 Post_subject:

Sylvander,

Use %T for hrs min secs in 24hr format.

Rob

Sylvander · Posted: Sat 30 May 2009, 09:03 Post_subject:

1. "You must set your Timezone geographically"
OK, it's now set to "London" and all is looking good. Very Happy

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.