On Thursday, 24 August 2017 13:48:59 BST Terry Coles wrote:
> On Thursday, 24 August 2017 12:51:38 BST Ralph Corderoy wrote:
> > ntp-wait(1) might be of interest: "This can be useful at boot time, to
> > delay the boot sequence until after ntpd -g has set the time".
>
> That is definitely of
On Thursday, 24 August 2017 12:51:38 BST Ralph Corderoy wrote:
> Where was this script? I forgotten upstart, but it probably still copes
> with scripts in /etc/init.d. If it's one of those, see update-rc.d(8).
> https://debian-handbook.info/browse/stable/unix-services.html#sect.system-bo
> ot
Hi Terry,
> I then did as Ralph originally suggested and stopped the NTP service
> from running. (I wasn't sure how to do this, so I added and exit 0 to
> the beginning of the script, which seemed to work OK. If there's a
> better way, I'd be interested to hear it.)
Where was this script? I
On Wednesday, 23 August 2017 19:42:02 BST Terry Coles wrote:
> On Wednesday, 23 August 2017 18:10:45 BST Terry Coles wrote:
> > I then executed 'sudo ntpd -q' after logging into buttspi. I've put the
> > screenshot of the results at:
> >
> > http://hadrian-way.co.uk/Misc/Butts_Pi_Screenshot.png
On Wednesday, 23 August 2017 18:10:45 BST Terry Coles wrote:
> I then executed 'sudo ntpd -q' after logging into buttspi. I've put the
> screenshot of the results at:
>
> http://hadrian-way.co.uk/Misc/Butts_Pi_Screenshot.png
>
> As you can see, the sync is quicker, but it still took nearly 5
On Wednesday, 23 August 2017 18:10:45 BST Terry Coles wrote:
> I then executed 'sudo ntpd -q' after logging into sumppi. I've put the
^^
On Wednesday, 23 August 2017 15:44:18 BST Terry Coles wrote:
> I've done a bit more research and discovered that it's not systemd that
> allows services to start in parallel, but upstart. Raspbian Stretch does
> use upstart, so I'm thinking that putting a delay in the ntp startup script
>
On Wednesday, 23 August 2017 14:30:12 BST Terry Coles wrote:
> Raspberry Pi Stretch is running systemd but the ntpd service file is
> installed in /etc/init.d. From this, I'm assuming that if I made a copy of
> the ntp.service file and put a delay into it, that would work, but will
> this delay
On Wednesday, 23 August 2017 10:35:16 BST Ralph Corderoy wrote:
> > If that proves to be the case, we'll have to delay for a while before
> > we do anything or put an RTC on the client Pi and only use NTP to sync
> > the two clocks.
>
> One used to use ntpdate(1) for a one-shot, set this
Hi Terry,
> > https://www.eecis.udel.edu/~mills/ntp/html/debug.html has some other
> > things to try.
>
> That last link has a lot of useful information (and even more in the
> links within that page).
It's probably just an online copy of the contents of the ntp-doc
package, and getting that
On Tuesday, 22 August 2017 17:36:34 BST Ralph Corderoy wrote:
> > http://hadrian-way.co.uk/Misc/Pi_NTP_Screenshot.png
>
> Were there any status characters in front of the `remote' IP address in
> the top left, do you recall?
I don't think so, but I've seen an asterisk in front of 127.127.1.0 (I
Hi Terry,
> I've examined the output of ntpq -pn, but it doesn't reveal anything
> to me that seems untoward, except that the both the Master and Remote
> Pis list 192.168.0.2 as the remote. See:
>
> http://hadrian-way.co.uk/Misc/Pi_NTP_Screenshot.png
Were there any status characters in front of
On Monday, 21 August 2017 16:32:12 BST Terry Coles wrote:
> For the Client we've added:
>
> server 192.168.0.2
>
> to the server pool.
>
> For the Server we've added:
>
> restrict 192.168.0.0 mask 255.255.255.0
>
> and:
>
>broadcast 192.168.0.255
>
> However, it doesn't work.
On Monday, 21 August 2017 17:30:18 BST Terry Coles wrote:
> > Add the following two lines to your servers config.
> >
> > server 127.127.1.0
> > fudge 127.127.1.0 stratum 12
>
> Hmmm. I tried that and still nogo. Should that have been 127.0.0.1? (I
> tried that and it still didn't
On Monday, 21 August 2017 16:56:50 BST Bob Dunlop wrote:
> Everything is sitting at stratum 16 "no trusted clocks", the server won't
> offer a syncronisation service at this level.
>
> The server needs a clock it trusts before it will serve the time.
>
> Add the following two lines to your
Hi,
On Mon, Aug 21 at 04:32, Terry Coles wrote:
...
> However, it doesn't work.
Everything is sitting at stratum 16 "no trusted clocks", the server won't
offer a syncronisation service at this level.
The server needs a clock it trusts before it will serve the time.
Add the following two lines
Hi,
We've been trying to set up a local NTP Server on our WMT network which
consists of a
Wireless AP (we're not connecting to the Internet), the 'Master' Pi and a
'Remote' Pi. The
Wireless AP is only there for debugging and to act as a Switch and the Pi's are
interconnected with Cat 5
17 matches
Mail list logo
