Re: [Dorset] Raspberry Pi Issue with hwclock

2017-09-16 Thread Ralph Corderoy
Hi Terry, > Anyone know how to get the message to delay? Assuming "display". :-) I don't have a Raspbian to poke about, but I'm assuming /etc/init.d/rc.local exists and it's what runs /etc/rc.local if it's executable. Make sure it is. If you're using `echo foo' then that goes to standard

Re: [Dorset] Raspberry Pi Issue with hwclock

2017-09-16 Thread Terry Coles
On Saturday, 16 September 2017 19:09:27 BST Bob Dunlop wrote: > exec rdate -v 192.168.0.2 Thanks. I copied some code from somewhere else ;-( Anyone know how to get the message to delay? -- Terry Coles -- Next meeting: Bournemouth, Tuesday, 2017-10-03 20:00 Meets,

Re: [Dorset] Raspberry Pi Issue with hwclock

2017-09-16 Thread Bob Dunlop
Hi, On Sat, Sep 16 at 06:16, Terry Coles wrote: ... > 2. I tried to put the command into an if structure to test to ensure that it > worked, eg > > if [ "rdate -v 192.168.0.2" ]; then > exit 0 > else > exit 1 > fi That's not the way to test the outcome of a command. The [ ] actually

Re: [Dorset] Raspberry Pi Issue with hwclock

2017-09-16 Thread Terry Coles
On Saturday, 16 September 2017 16:53:24 BST Ralph Corderoy wrote: > Some ports provide such trivial functionality that inet and xinetd do > the work themselves, and TCP and UDP port 37 is one of those. > https://en.wikipedia.org/wiki/Xinetd gives some more detail, and its > worked example is an

Re: [Dorset] Raspberry Pi Issue with hwclock

2017-09-16 Thread Terry Coles
On Saturday, 16 September 2017 17:05:27 BST Ralph Corderoy wrote: > Out of curiousity, what rebooted? Both devices. They both derive their power from the same 19 V PSU. -- Terry Coles -- Next meeting: Bournemouth, Tuesday, 2017-10-03 20:00 Meets, Mailing list, IRC,

Re: [Dorset] Raspberry Pi Issue with hwclock

2017-09-16 Thread Ralph Corderoy
Hi Terry, > The RTC kept perfect time. I then enabled 'broadcastclient' on [the > client] and on the next reboot the time on [the server] was reset to > the same (or nearly the same) as [the client]. Out of curiousity, what rebooted? Cheers, Ralph. -- Next meeting: Bournemouth, Tuesday,

Re: [Dorset] Raspberry Pi Issue with hwclock

2017-09-16 Thread Ralph Corderoy
Hi Terry, > sudo rdate -v 192.168.0.2 > > and got connection refused. That tells you that the remote network stack replied saying there was nothing that was listening on the port you tried to contact. > Apparently, (according to the rdate man page), the time source 'is > usually implemented

Re: [Dorset] Raspberry Pi Issue with hwclock

2017-09-16 Thread Terry Coles
On Monday, 11 September 2017 15:14:43 BST Ralph Corderoy wrote: > You might find an rdate(1) from the slave is simpler at boot time. I > don't know if Raspbian provides a server for the `time' port, but it's a > trivial thing. Well. I took your advice and started from a clean installation of