Time sync

[tawalker]

I was wondering what NTP clients exist for the Zaurus - that is, for sync\'ing the system clock with an Internet time server. ISTR there\'s a commercial program on Handango (\"Drifter\"?), but are there any alternatives (command-line or graphical)?

Many thanks,
Tim

[doseas]

Hint: Googling \"Zaurus NTP\" turned up several hits.

It looks like there is a copy of ntpdate here, with instructions:
 www.geocities.co.jp/SiliconValley-Bay/1180/download.html
(use Babelfish to translate)

I found a beta copy of qpe-ndate, with source code, here:
  http://www.oeste.de/download/

I haven\'t tested these, so use at your own risk...

[Anonymous]

are there any alternatives (command-line or graphical)?

I run this shell script from an icon. (only good for USA time zones)
Substitute for your location.

# cat runtime.sh
#!/bin/sh
$QPEDIR/bin/evm -Xprogress:2000 -XappName=runtime.sh -appletviewer http://nist.time.gov/timezone.cgi?Hawaii-A...tian/d/-10/java
#

[allyrfriends]

Opie\'s date and time settings application has an option to use NTP; it comes as standard on OZ. I\'m pretty sure this is the command line NTP program used by Open Zaurus and that it would probably work on a Sharp ROM but I\'m not promising.

[Anonymous]

http://docs.zaurus.com/feed/rdate_1.3-3_arm.ipk

[Anonymous]

Frontend for rdate to get a servers time
http://docs.zaurus.com/feed/synchronizeclo...ock_1.0_arm.ipk

[Anonymous]

It works.

# rdate -p 132.163.4.101
Thu Dec 18 02:19:52 2003

[Anonymous]

Frontend for rdate to get a servers time

This works if it runs with root privilege. I tried server NIST server 132.163.4.101

[Anonymous]

The time is wrong with rdate after suspend and resume. I need to set the time in the Date/Time application.

[Anonymous]

Thanks to doseas for finding an app that works.

ntpdate_ntp-4.1.1b-z-4_arm works and the time holds after suspend/resume. I also installed rdate.

[Anonymous]

# ntpdate 132.163.4.101
18 Dec 05:05:46 ntpdate[12358]: step time server 132.163.4.101 offset 240253.508038 sec
Write to trigger.
# date
Thu Dec 18 05:06:33 UTC 2003
#
sucess!

Sorry for all the posts.

[Anonymous]

The correct date holds after reboot. ntpdate must change the hardware clock. You don\'t need rdate for ntpdate to work. Now I can assign an icon to the ntpdate script.

[tawalker]

Thanks for the multitude of suggestions here - I\'ll give them a try!

Tim

[Anonymous]

Here are two scripts to run ntpdate. Call runntpdate from an icon.

# pwd
/home/QtPalmtop/bin
# cat runntpdate
#!/bin/sh
qcop QPE/Application/embeddedkonsole \'setDocument(QString)\' \'/home/QtPalmtop/bin/setntpdate.sh\'
exit 0
#
# cat setntpdate.sh
#!/bin/sh
su -c \'/home/root/usr/bin/ntpdate 132.163.4.101\'
echo set date/time with ntpdate
date
exit 0
#

output looks like this in embeddedkonsole.

$ su -c \'/home/QtPalmtop/bin/setntpdate.sh\'
Password:
18 Dec 14:30:03 ntpdate[1237]: adjust time server 132.163.4.101 offset -0.008508 sec
Write to trigger.
set date/time with ntpdate
Thu Dec 18 14:30:03 UTC 2003
$

[Anonymous]

You can use rdate to set the software clock and sync the hardware clock.

Sending a command to the pipe /var/spool/at/trigger causes the hwclock to sync up with the software clock. That is what ntpdate does.

# rdate 132.163.4.101
# echo \'W\' ] /var/spool/at/trigger

I verified that the adjusted date and time hold after suspend/resume and after reboot.