From owner-freebsd-current Fri Jul 19 23:13:35 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3847437B400 for ; Fri, 19 Jul 2002 23:13:32 -0700 (PDT) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6A3143E4A for ; Fri, 19 Jul 2002 23:13:31 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.12.5/8.12.4) with ESMTP id g6K6DVCV012112; Fri, 19 Jul 2002 23:13:31 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.5/8.12.4/Submit) id g6K6DVfJ012111; Fri, 19 Jul 2002 23:13:31 -0700 (PDT) (envelope-from dillon) Date: Fri, 19 Jul 2002 23:13:31 -0700 (PDT) From: Matthew Dillon Message-Id: <200207200613.g6K6DVfJ012111@apollo.backplane.com> To: "WB Support" Cc: "Gavin Atkinson" , Subject: Re: getting vmemoryuse resource limit: Invalid argument References: <11358D68-9B47-11D6-800F-000393754B1C@vangelderen.org> <03ce01c22f5e$ba1b0740$11fd2fd8@ADMIN00> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :> >>> Jul 18 09:21:24 epsilon login: getting vmemoryuse resource limit: :> >>> Invalid argument :> >> :I had the same problem on a 4.6-STABLE system due to not installing an :updated kernel with support for this resouce limit. : :Usually, I do a "buildworld, buildkernel, installkernel, mergemaster, :installworld", but that day I forgot to do an "installkernel". I found my :mistake by checking the date on the /kernel file. : :Check if your /kernel is uptodate with your installworld. : :Scot A couple of people have run up against this. I think it's worth at least an entry in UPDATING and I will do so. I don't know if it's worth adjusting login / other programs to not die a horrible death if they can't find the resource. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message