Date: Wed, 9 Mar 2016 09:59:47 -0600 From: Eric van Gyzen <eric@vangyzen.net> To: Brendan Sechter <sgeos@hotmail.com>, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: limits: setrlimit umtxp: Invalid argument Message-ID: <56E04873.9050200@vangyzen.net> In-Reply-To: <BAY182-W54B92C21428A30D70FA5C9A2B30@phx.gbl> References: <BAY182-W54B92C21428A30D70FA5C9A2B30@phx.gbl>
index | next in thread | previous in thread | raw e-mail
On 03/09/2016 09:49, Brendan Sechter wrote: > I am running an 11.0-CURRENT VM. > After recently updating, the following appears on startup and dhclient fails to start. > > Starting dhclient. > limits: setrlimit umtxp: Invalid argument > /etc/rc.d/dhclient: WARNING: failed to start dhclient > > Similar messages appear for the following. > > devd pflog syslogd ntpd powerd sshd sendmail_submit sendmail_msp_queue cron > > Reverting to the previous kernel did not resolve the issue. > I can manually start dhclient and ntp, but not sshd. > > I do not trust that my uname information is being updated with with build, but here > it is. > > $ uname -vm > FreeBSD 11.0-CURRENT #0 r287598: Thu Sep 10 14:45:48 JST 2015 root@:/usr/obj/usr/src/sys/MIRAGE_KERNEL amd64 This information comes directly from the running kernel, so it looks like your kernel is not getting updated. This seems consistent with the above error messages, although I haven't tested this case. The userland tools are aware of the newly added umtxp limit, but the kernel is not aware. Erichelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56E04873.9050200>