Date: Sat, 20 Jul 2002 10:42:24 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> To: "Scot W. Hetzel" <hetzels@westbend.net> Cc: "Gavin Atkinson" <gavin@ury.york.ac.uk>, <freebsd-current@FreeBSD.ORG> Subject: Re: getting vmemoryuse resource limit: Invalid argument Message-ID: <200207201742.g6KHgObZ037993@apollo.backplane.com> References: <11358D68-9B47-11D6-800F-000393754B1C@vangelderen.org> <03ce01c22f5e$ba1b0740$11fd2fd8@ADMIN00> <200207200613.g6K6DVfJ012111@apollo.backplane.com> <002101c22ffb$293d1180$12fd2fd8@Admin01>
next in thread | previous in thread | raw e-mail | index | archive | help
:> 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
Ah, ok. Since it isn't fatal I don't think we need to adjust the
source code (e.g. to things like login) to deal with older kernels.
-Matt
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?200207201742.g6KHgObZ037993>