Greg Erskine wrote:
> If you are using pCP8, then refer to this post:
>
> 'Announce: piCorePlayer 8.0.0 - Network Timing Protocol'
> (https://forums.slimdevices.com/showthread.php?115268-Announce-piCorePlayer-8-0-0-Network-Timing-Protocol)
>
> By default, pCP should keep "reasonable" time, just
If you are using pCP8, then refer to this post:
'Announce: piCorePlayer 8.0.0 - Network Timing Protocol'
(https://forums.slimdevices.com/showthread.php?115268-Announce-piCorePlayer-8-0-0-Network-Timing-Protocol)
By default, pCP should keep "reasonable" time, just drifting a few
seconds a day.
Greg Erskine wrote:
> Thanks Paul, 2 to 4 seconds.
>
> Has anyone tried adding "/usr/sbin/ntpd -p pool.ntp.org" to a User
> command?
>
> This adds a ntpd daemon but as I don't have an issue I haven't proved it
> works.
>
> EDIT: It works. I booted without a network cable, so time set to epoch
Thanks
Greg Erskine's Profile: http://forums.slimdevices.com/member.php?userid=7403
View this thread: http://forums.slimdevices.com/showthread.php?t=112335
___
unix mailing list
Greg Erskine wrote:
> Has anyone worked out the actual time drift of a Raspberry Pi?My 4B seems to
> drift less than 2 seconds per day.
Code:
$ date
Sat Jan 16 21:15:23 CET 2021
tc@piCoreServer:/etc/sysconfig$ sudo /usr/bin/getTime.sh
tc@piCoreServer:/etc/syscon
Tx for the info - understand about keep the distro small. The trouble
is, once you start adding server-y type apps e.g. LMS, or a clock
display on a system without a RTC, then they often need other server-y
things to run reliably. A victim of it's own popularity! ;-)
Not sure if it'd be possible
hi mr-b,
Yes it is that easy.
To summarize.
1. Run ntpd once at boot.
This assumes that there is a working network that can access a time
server on the internet.
This is how TinyCore/piCore/piCorePlayer works by default. This works
fine 99% of the time.
Possible issues:
- time drifts of a
When you run it that way it is always running - so you can use "top" or
similar to see what resources it is consuming.
Most of the time it will be sleeping.
Paul Webster
http://dabdig.blogspot.com
author of \"now playing\" plugins covering radio france (fip etc), kcrw,
supla finland, abc austr
I didn't realise that was all it was!
So I just put that cmd in Tweaks > User Commands?
How often does it run i.e. is it more onerous than the cron job? I
coudn't find that definitive info on that - other than "only one query
every 1024 seconds (or longer)".
Thanks Paul, 2 to 4 seconds.
Has anyone tried adding "/usr/sbin/ntpd -p pool.ntp.org" to a User
command?
This adds a ntpd daemon but as I don't have an issue I haven't proved it
works.
Greg Erskine's Profile: http://foru
FYI - I found RPi drifts about 2 to 4 seconds per day.
While that might be critical for some applications I find that it is not
an issue when using it as a player or server - and a once a day
cron-based time sync stops that drift going too far.
Paul Webster
http://dabdig.blogspot.com
author of
I've been using 2 RPi4B's since their release, can't remember one
occasion when the date wasn't set. So we need to find what's out the
different with your RPi4B.
If you reboot, and the problem is still there, the cron job will only
fix the problem once it runs.
Did you try running ntpd as a dae
Ok I'm stumped - it's gone back to epoch again , even with the cron
entry. :-(
~$ date
Thu Jan 1 04:14:31 GMT 1970
mr-b's Profile: http://forums.slimdevices.com/member.php?userid=10044
View this thread: http://forums.sli
A couple of things that I tried before but have just confirmed.
You can't set date quite to epoch, 1970-01-03 is OK. If you try to set
the earliest date in epoch seconds, you will find it actually changes.
When running ntpd as a daemon, it will only adjust time from a large
delta once. So if yo
Useful info - will have a look at ntpd daemon but configuring that is a
fair way outside my knowledge.
Appreciate PCP is a minimal system but if it's going to run LMS and
assuming all the network ducks are in a row for UDP only at boot time
sounds like setting up for a fall. Heaven forfend if Ker
mr-b wrote:
> Yes I've added a cron job a while back, but only after installing 6.1.0
> and some investigations on weird LMS behaviour (I thought it might be
> the 8.0 beta) that eventally led to time sync being the smoking gun, and
> then seeing others reporting it too - hence my suggestion for
mr-b wrote:
> Yes I've added a cron job a while back, but only after installing 6.1.0
> and some investigations on weird LMS behaviour (I thought it might be
> the 8.0 beta) that eventally led to time sync being the smoking gun, and
> then seeing others reporting it too - hence my suggestion for
Yes I've added a cron job a while back, but only after installing 6.1.0
and some investigations on weird LMS behaviour (I thought it might be
the 8.0 beta) that eventally led to time sync being the smoking gun, and
then seeing others reporting it too - hence my suggestion for making it
standard f
If you want it, then add it, there are provisions to do it. As Paul W
mentioned once a day or two is plenty often enough. If you were really
worried about it at boot, then you would add a RTC to the pi.
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picorep
I've run a few more tests and NTP seems pretty spotty (I tried
0.uk.pool.ntp.org and it was even worse!) and it is send and pray (UDP),
so I think this might explain why folks are having trouble with a one
shot attempt at boot time.
LMS particularly doesn't like time issues, so there could be a c
Maybe you were unlucky and pool.ntp.org picked a temporarily unreachable
server.
In theory it should not matter much as eventually it will get one and
the time should then remain roughly correct (RPi does drift time) so
running it every few hours or days via cron should be enough to keep
things w
Tx - I don't understand the output though - other than the inconsistency
of results doesn't look good.
Code:
tc@PCP-XLR-LMS:~$ cat /etc/sysconfig/ntpserver
pool.ntp.org
tc@PCP-XLR-LMS:~$ sudo /usr/sbin/ntpd -n -d -p pool.ntp.org
ntpd: 'pool.ntp.org' is 21
Since we don't run a syslog, verbose only works when not daemonizing.
Add the -n option to see what's up.
Secondly, you telling ntpd to use "-d" as your server. Your server
needs to follow the -p
sudo /usr/sbin/ntpd -n -d -p 0.uk.pool.ntp.org
piCorePlayer a small player for the Raspberr
I tried running the cmd sudo /usr/bin/getTime.sh but it outputs
nothing. I searched for help on the ntpd cmd but I'm afraid I was lost
rather.
cat getTime.sh
#!/bin/busybox ash
# bmarkus - 26/02/2014
NTPSERVER=$(cat /etc/sysconfig/ntpserver)
/usr/sbin/ntpd -q -p $NTPSERVER
Then I tried runnin
I think you need to redirect the output to a file (if it generates
any).
Name the file something like pcp_blah_blah.log in /var/log and it will
display in [Diagnostics] > [Logs] as "blah blah".
Greg Erskine's Profile: htt
There would not be logging by default, unless your cron script directed
output to a log file.
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
(https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=U7JHY5WYHCNRU&lc=GB¤cy_
How can I check that the cron job is running successfully (ntpd cmd)?
Not sure which log I should be viewing but I couldn't see any cron log
files in /var/log. Or does the script have to be modded to output to a
specific file?
Sheesh, I'm so rusty on Unix.
--
paul- wrote:
> Yes, go to the Extras-> Bootcodes page (In beta mode) There is an ntp
> option.
Would be nice if this could be set by DHCP option 42 :)
Jeff
*Players:* SliMP3,Squeezebox3 x3,Receiver,SqueezeLite-X,PiCorePlayer x3
*Server:* LMS Version: Latest Nightly on Centos 8.0 VM on ES
paul- wrote:
> Yes, go to the Extras-> Bootcodes page (In beta mode) There is an ntp
> option.
Perfect thanks - just what I was looking for!!
farrina's Profile: http://forums.slimdevices.com/member.php?userid=65601
View
farrina wrote:
>
> I presume you can manually set an internal NTP server IP address
> somewhere (I guess the only issue may be it being overwritten by an
> update).
Yes, go to the Extras-> Bootcodes page (In beta mode) There is an ntp
option.
piCorePlayer a small player for the Raspberry
farrina wrote:
> Im a member of the tin foil hat brigade
Not sure that is particularly true, limiting outbound connections is a
security step that many do but you have to have the knowledge and
equipment to do it.
Jeff
*Players:* SliMP3,Squeezebox3 x3,Receiver,SqueezeLite-X,PiCorePlayer x
Paul Webster wrote:
> pCP 6 does try to wait for the time to come ... but I guess it did not
> wait long enough for you.
>
> What I have in mine is a crontab entry that syncs the time every day at
> 6am
> >
Code:
> >
> 0 6 * * * /usr/bin/getTime.sh
>
-
farrina wrote:
> I am experimenting with piCorePlayer on a raspberry Pi3B. Date wise it
> would appear that I am stuck in the 1970's !
>
> Is it possible to configure a local (internal) NTP server from within
> piCorePlayer such that on an (infrequent) reboot it will automatically
> update?
>
pCP 6 does try to wait for the time to come ... but I guess it did not
wait long enough for you.
What I have in mine is a crontab entry that syncs the time every day at
6am
Code:
0 6 * * * /usr/bin/getTime.sh
You can set this in the crontab
I am experimenting with piCorePlayer on a raspberry Pi3B. Date wise it
would appear that I am stuck in the 1970's !
Is it possible to configure a local (internal) NTP server from within
piCorePlayer such that on an (infrequent) reboot it will automatically
update?
Cheers
Software versions thus
35 matches
Mail list logo
