Date: Sat, 20 Jul 2002 09:38:48 -0500 From: "Scot W. Hetzel" <hetzels@westbend.net> To: "Matthew Dillon" <dillon@apollo.backplane.com> Cc: "Gavin Atkinson" <gavin@ury.york.ac.uk>, <freebsd-current@FreeBSD.ORG> Subject: Re: getting vmemoryuse resource limit: Invalid argument Message-ID: <002101c22ffb$293d1180$12fd2fd8@Admin01> References: <11358D68-9B47-11D6-800F-000393754B1C@vangelderen.org> <03ce01c22f5e$ba1b0740$11fd2fd8@ADMIN00> <200207200613.g6K6DVfJ012111@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
From: "Matthew Dillon" <dillon@apollo.backplane.com> > :> >>> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?002101c22ffb$293d1180$12fd2fd8>