From owner-freebsd-current Sat Jul 20 7:39: 6 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 7D4FC37B400 for ; Sat, 20 Jul 2002 07:39:04 -0700 (PDT) Received: from mail.westbend.net (ns1.westbend.net [216.47.253.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id C76A843E64 for ; Sat, 20 Jul 2002 07:39:03 -0700 (PDT) (envelope-from hetzels@westbend.net) Received: from Admin01 (admin01.westbend.net [216.47.253.18]) by mail.westbend.net (8.12.5/8.12.5) with SMTP id g6KEd1lG010225; Sat, 20 Jul 2002 09:39:01 -0500 (CDT) (envelope-from hetzels@westbend.net) Message-ID: <002101c22ffb$293d1180$12fd2fd8@Admin01> From: "Scot W. Hetzel" To: "Matthew Dillon" Cc: "Gavin Atkinson" , References: <11358D68-9B47-11D6-800F-000393754B1C@vangelderen.org> <03ce01c22f5e$ba1b0740$11fd2fd8@ADMIN00> <200207200613.g6K6DVfJ012111@apollo.backplane.com> Subject: Re: getting vmemoryuse resource limit: Invalid argument Date: Sat, 20 Jul 2002 09:38:48 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Virus-Scanned: by amavisd-milter (http://amavis.org/) 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 From: "Matthew Dillon" > :> >>> 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. > They don't die a horrible death, as it is only the kernel reporting that the vmemoryuse resource limit is not in the installed kernel. The programs continue to function, as I was able to login without any problems. It's just that each time a program (cron, login, inetd, sshd, su, ...) tried to set this limit, the error message was reported on the console and the log file.. Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message