Running a Time Sync Daemon to avoid NFS delays (Duo v.1.)?

I found this with a search, anyone had any experience with it?

http://readynasfreeware.org/projects/nas-ntpserver

Will it run on the Duo v.1. ?

handy wrote:
My questions are, is there a method for setting up the ReadyNAS Duo v.1. to be the LAN time server? If so how? If the unfortunate situation is that it is not possible, then the next question is how do you get the Duo to run a time sync daemon & accept one of the other machines as the time server?

The Duo v1 lets you configure its time server (click in system in frontview, then clock).

There is also an old add-on for the v1 here: viewtopic.php?f=47&t=33964&p=187161&hilit=time+server#p187161 I am not sure if it still functions properly.

StephenB wrote:

handy wrote: My questions are, is there a method for setting up the ReadyNAS Duo v.1. to be the LAN time server? If so how? If the unfortunate situation is that it is not possible, then the next question is how do you get the Duo to run a time sync daemon & accept one of the other machines as the time server? The Duo v1 lets you configure its time server (click in system in frontview, then clock). There is also an old add-on for the v1 here: viewtopic.php?f=47&t=33964&p=187161&hilit=time+server#p187161 I am not sure if it still functions properly.

Thanks StephenB, your post was very helpful.

The frontview system/clock was set up correctly already (good luck I guess, I'd forgotten all about it). The link to WhoCares? , post was particularly helpful, as it is his add-on that I have installed. Just those few words on his post should be (those famous words) all that I need to know.

I'll post back one way or another in the future.

Thanks again.

Well I think that WhoCares? NTP-server add-on is working fine on my Duo v.1.

I've only set up a Manjaro Linux (based on Arch) box to use it thus far, following is the output from the recently booted Manjaro using this alias in ~/.bashrc :

alias time="timedatectl status && ntpq -c lpeer"

[handy@jarmano ~]$ time
      Local time: Wed, 2012-11-14 14:40:48 EST
  Universal time: Wed, 2012-11-14 03:40:48 UTC
        RTC time: Wed, 2012-11-14 03:40:48
        Timezone: Australia/Sydney
     NTP enabled: yes
NTP synchronized: yes
 RTC in local TZ: no
     remote           refid      st t when poll reach    
=====================================================
*192.168.1.15    203.170.87.4     3 u    3   64  377    

delay   offset   jitter
========================
0.205  45.678   33.251

Note: I've edited the output above, as it exceeded the character number limitations placed on the length of lines by this forum software, hopefully it doesn't turn into an illegible mess when viewed with different screen resolution/font sizes.

I dual boot Linux/Win7, which has been a pain in the neck, as the registry tweeks to get Win7 to use UTC, don't work on my machine. I don't have any need for the Win7 box to talk to the Duo, BUT, every time I do boot into Win7, it messes up the RTC time, due to its not knowing how to handle daylight saving, which was of course carried through to the prime system on that machine - Linux or PC-BSD.

At last I found an excellent solution:- I've installed NTP on Win7, following this superb how-to:

http://www.satsignal.eu/ntp/setup.html

I expect that someone is going to be happy to have found that solution.

[edit:] I almost forgot <doh!> the prime reason for my running down this local NTP-server path was to see if having the Duo & my Linux box's time in sync would get around the ~60 second delay the Linux box is having during boot. It has no effect, on that problem (for me) I'm sorry to say.