Date: Sat, 28 Jun 2014 06:03:16 +0200 From: Hans Petter Selasky <hps@selasky.org> To: Danilo Egea <daniloegea@yahoo.com.br>, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: sysctl: Cannot allocate memory after r267961 Message-ID: <53AE3E84.5030106@selasky.org> In-Reply-To: <53AE3989.9020000@selasky.org> References: <1403895102.10070.YahooMailNeo@web162001.mail.bf1.yahoo.com> <53AE3989.9020000@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 06/28/14 05:42, Hans Petter Selasky wrote: > On 06/27/14 20:51, Danilo Egea wrote: >> Hello folks, >> >> I've just updated my system (current) and now I'm getting this message: >> [danilo src$] uname -a >> uname: sysctl: Cannot allocate memory >> >> >> Some programs are failing due this, like portmaster and chromium. >> >> This commit (r267961) has a lot of changes in the sysctl subsystem. >> >> Thanks! > > Hi folks, > > Sorry about the breakage. There appears to be some special case for > read-only MIB SYSCTL strings which was ending up in an error code that's > not so well documented. Sorry that it is not possible for me to test > absolutely everything. > > Testing done from my side: > > - Several universe builds > - Sysctl functionality has been verified and tested. > > I'm going to pull in the change again with the fix for "uname". If there > are more problems popping up I need your help to test this patch. > > Thanks for your patience! > > --HPS Fixed in: r267992 --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53AE3E84.5030106>