On Wed, Aug 08, 2018 at 08:20:54PM -0700, Jonathan Hull wrote:
> Note that this is just a project build folder, and things next get
> installed into the image project by Yocto.
> There ‘workdir’ there is something like:
>
> ‘/home/sanderson/jethro/mercury/tmp/work/mercury-poky-linux-gnueabi/core-i
It does appear to be from Chrony. Tonight one of our developers appears to
have a solution around the issue, which may be induced by us. Sorry to
waste people's time if that is the case. Details of our findings are posted
below since I first posted here, but will move over to the Chrony project
and
On Wed, Aug 08, 2018 at 02:47:01PM -0700, Jonathan Hull wrote:
> Fatal error : Unix socket path too long
That message must be coming from chronyd. Miroslav?
Thanks,
Richard
--
Check out the vibrant tech community on one
I have a couple of systems successfully running Chrony and the LinuxPTP package
using the Timemaster service. These systems are Intel and ARM based showing no
issues and work well. A new embedded device that is ARM based is in the process
of bring up with a Yocto variant of Linux giving me an od
Pardon me if this is a duplicate. Had trouble posting to the forum.
I have a couple of systems successfully running Chrony and the LinuxPTP
package using the Timemaster service. These systems are Intel and ARM based
showing no issues and work well. A new embedded device that is ARM based is
in the
