Doyle Glaze wrote:
> In e-smith4.0 you are able to setup the sync with a external
> time server.
>
> Question 1: How do you know if and when the times are being
> synced?
I noticed lines in /var/log/messages like these:
Sep 28 11:17:27 e-smith xntpd[448]: synchronisation lost
Sep 28 11:17:27 e-smith xntpd[448]: synchronized to 193.204.114.231, stratum=1
Sep 28 11:17:27 e-smith xntpd[448]: kernel pll status change 89
If I understand well, they signal a clock drift in the server, corrected via NTP from the reference server. And that the NTP server works, too...

> Question 2: When I use a windows program i.e atomic clock and
> set it to sync with e-smith it does net sync.
Trying to sync a Linus box to the E-Smith Server, I noticed that the rdate command generates a "Connection refused" error. I guess that this could be the source of your ptoblem too.
Otherwise, the Linus box get sync-ed correctly using its xntpd daemon and NTP protocol.
How often do you need to update the Windows PC clock? How often do you reboot the Windows PC?
You could try a PC-NTP software, if it exists.
If you don't need a more frequent time sync than once every reboot, you could try to write a simple batch file containing the following command:
net time \server /set /yes
where "server" is the E-Smith Server name, and put a link to it in the Start menu startup folder.
--
Pierluigi Miranda
Cerveteri (Roma)
p.miranda@mclink.it