I have a little Soekris box whose ONLY task is to get the time from
a simple DCF77 time signal receiver and redistribute it with NTP.
The update from 10.1 to 10.2 has broken this functionality.
The relevant ntp.conf configuration...
server 127.127.8.0 mode 14
fudge 127.127.8.0 time1 0.235
... no
On Sat, 2015-08-15 at 15:46 +, Christian Weisgerber wrote:
> I have a little Soekris box whose ONLY task is to get the time from
> a simple DCF77 time signal receiver and redistribute it with NTP.
> The update from 10.1 to 10.2 has broken this functionality.
>
> The relevant ntp.conf configura
just upgraded from 10.1-RELEASE-p16 to 10.2-RELEASE using freebsd-update.
after the upgrade, I began getting errors because pam_opie.so.5 has an
unsatisfied link to libopie.so.7 (my system only has libopie.so.8).
I notice a fresh install of 10.2-RELEASE does indeed contain libopie.so.7,
so I'm cu
I actually have the exact same problem, but worked around by creating a
symlink. My libopie.so.8 has the exact same properties as yours (file length
and date).
I also did a small diff on the checksums in /usr/lib compared to the release
build:
$ diff base.txt jail.txt
12,13c12,13
< SHA256 (dt
On 08/14/2015 12:39 PM, Warren Block wrote:
> On Fri, 14 Aug 2015, Tim Daneliuk wrote:
>
>> I just built a 10.2 machine on a cloud-based VPS (Digital Ocean) that has
>> 512M of memory and 1G of swap partition. I am seeing a ton of errors like
>> this:
>>
>> Aug 14 00:01:22 myhost kernel: swap_pag
Michael B. Eichorn:
> Dunno as to what happened with ntp or how to fix it, but there are a
> couple other ntp soultions in ports that might work.
>
> NTP is known to be very complex, IIRC phk@ is being paid by the Linux
> Foundation to write a replacement, ntimed.
At this time, ntimed is an NTP
On 08/12/2015 04:44 PM, Roosevelt Littleton wrote:
Hi,
So, I can confirm with the attached patch. I have a working msk0 that
hasn't failed for the past month. I considered this problem fix for me.
Since, I have went a long time without any problems. Thanks!
Roosevelt