From owner-freebsd-current@freebsd.org Wed Mar 9 15:59:48 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D7927AC9E2E for ; Wed, 9 Mar 2016 15:59:48 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from smtp.vangyzen.net (hotblack.vangyzen.net [199.48.133.146]) by mx1.freebsd.org (Postfix) with ESMTP id C2B79D0A for ; Wed, 9 Mar 2016 15:59:47 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from sweettea.beer.town (unknown [76.164.8.130]) by smtp.vangyzen.net (Postfix) with ESMTPSA id 9BFA556A6D; Wed, 9 Mar 2016 09:59:47 -0600 (CST) Subject: Re: limits: setrlimit umtxp: Invalid argument To: Brendan Sechter , "freebsd-current@freebsd.org" References: From: Eric van Gyzen Message-ID: <56E04873.9050200@vangyzen.net> Date: Wed, 9 Mar 2016 09:59:47 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Mar 2016 15:59:48 -0000 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. Eric