(old)Puppy Linux Discussion Forum

Psync just doesn't work for me. I choose the North America server. Psync seems to be doing something and doesn't report any errors, but when all is said and done, the time displayed in the lower right corner doesn't change even though it might be a minute or more off according to http://time.gov/

I haven't reported this because I don't see how what I have to say will be of any use. If there's anything I can do that will help figure out why Psync doesn't work for me, let me know and I'll try to do it.

Version 1.6

Flash,

have you tried manually changing your clock by a few minutes and then run psync.

Please let me know if it doesn't alter.

I tried it and used NA and it worked.

I set the clock 7 minutes ahead according to time.gov, then told Psync to set the clock from the North American time server. Psync reported back that it did, but the end result was the same time as before - the time displayed by my computer is 7 minutes fast. Psync may be setting a clock somewhere in my computer, but that time is not showing up on my display.

I know there are system clocks and other kinds, and UTC and so forth. I never paid attention to the explanations and discussions of the many different kinds of time a computer can keep, because why the hell can't everyone agree on one simple way for a computer to keep time? Sheesh.

Psync 1.8 released.

Not sure if this suits everyone, it will take notice of UTC setting if you wish.

The trade off is the opening screen includes approx. .9 second software latency added to the report. However the sync button report is accurate.

Psync-2.0

A more accurate opening report with no latency added.

The final sync report is accurate as processing has finished.

Psync 2.1 released.

This generates a report window from the temporary file.

echo -e"EUROPEREP" >> /usr/local/psync/setcoutry

Line 41 of /usr/local/psync/psyncfunc
(default installation in lucid 525)

Line 66 in the newest version.

Bug causes autostart to fail if person is from europe.

Exactly.
I asked for help in the IRC channel and rltz was a good chap and found the issue with the command syntax in line 66.
Could you please have this fixed for the next release?
Thanks for your help.
Cheers

OK guys thanks for this.

I see a space is missing causing the problem.

I'll release an update.

Corrected version 2.2 posted.

Thanks Rob .
Cheers

Version 2.3 released to fix the report window for time offset.

Fatdog 64 bit version posted.

Psync 2.4 version.

I've added the Daylight Savings dates if applicable to timezone.

I haven't checked all timezones for which ones don't apply DST so there may be an odd entry in the filed.

Version 2.5

Added code to check for DST not applying to a timezone.

Version 2.6

Sorry if this is a bit quick on the heels of 2.5

The time servers report back has changed in text length several times. This required a minor rewrite each time, as the report window contained 'bits' of extraneous text.

Now I believe I have trapped a change in text length and compensated for it.

This means no more minor releases just for that.

This issue has always annoyed me.

Version 2.6-64 for 64bit systems such as FatDog etc

Slacko needs zdump adding to /usr/bin directory. See first page.

Hi,

Psync doesn't set the RTC on my Lupu525 because of two HWCLOCKTIME in the /etc/clock file: Although the last line is commented out, 'HWCLOCKTIME' still matches it. As a result $HTIME is set to "localtime utc" and the hwclock command is never executed. I don't know how this file looks in other Puppies. Maybe '^[[:space:]]*HWCLOCKTIME' or simply '^HWCLOCKTIME' would be a better choice here.