> On Mon, Jun 12, 2017 at 10:14 AM, John Baldwin wrote:
> > On Sunday, June 11, 2017 11:12:25 AM David Wolfskill wrote:
> >> On Sun, Jun 04, 2017 at 08:57:44AM -0400, Michael Butler wrote:
> >> > It seems that {rpc.}lockd no longer runs after the ino64 changes on any
> >> > of
Dear hackers,
I couldn't find a up to date list for begning LOR reports. Since
ffs/vfs.. LORs, which I don't understand, diffused my attention over the
time, I'm not aware about the actual importance of them these days
(without panic).
Here's is one, happening on 11.1-BETA1. which I haven't
On 12 June 2017 at 00:43, Warner Losh wrote:
>
> aarch64 support isn't completely integrated into FreeBSD 11 yet.
A clarification: arm64/aarch64 support has been available as of
FreeBSD 11.0 for Cavium ThunderX, and the SoftIron arm64 hardware is
also supported now.
What we
On Mon, Jun 12, 2017 at 10:14 AM, John Baldwin wrote:
> On Sunday, June 11, 2017 11:12:25 AM David Wolfskill wrote:
>> On Sun, Jun 04, 2017 at 08:57:44AM -0400, Michael Butler wrote:
>> > It seems that {rpc.}lockd no longer runs after the ino64 changes on any
>> > of my systems
On Sunday, June 11, 2017 11:12:25 AM David Wolfskill wrote:
> On Sun, Jun 04, 2017 at 08:57:44AM -0400, Michael Butler wrote:
> > It seems that {rpc.}lockd no longer runs after the ino64 changes on any
> > of my systems after a full rebuild of src and ports. No log entries
> > offer any insight as
On Mon, Jun 12, 2017 at 12:24:58AM -0700, Xin Li wrote:
> Thanks for Kostantin's hints, this is indeed related to my change (which
> exposed an old bug with rpc.lockd).
>
> Please try attached fix.
>
Aye; that appears to do the job:
freebeast(11.1)[1] uname -a && service lockd status
Thanks for Kostantin's hints, this is indeed related to my change (which
exposed an old bug with rpc.lockd).
Please try attached fix.
Cheers,
Index: usr.sbin/rpc.lockd/lockd.c
===
--- usr.sbin/rpc.lockd/lockd.c (revision 319826)