Date: Sun, 18 Mar 2001 21:04:00 -0800 (PST) From: Matt Dillon <dillon@earth.backplane.com> To: Jonathan Lemon <jlemon@flugsvamp.com> Cc: stable@FreeBSD.ORG Subject: Re: Not only ftpd's problem with ls */../*..... Message-ID: <200103190504.f2J540A03836@earth.backplane.com> References: <local.mail.freebsd-stable/200103172107.f2HL7Ea02611@cwsys.cwsent.com> <200103172253.f2HMrZ008412@prism.flugsvamp.com> <200103180027.f2I0RSn96769@earth.backplane.com> <20010317222918.B82645@prism.flugsvamp.com> <200103180543.f2I5hb398084@earth.backplane.com> <20010318160034.F82645@prism.flugsvamp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
:And this differs in what way from having limit impose a hard resource
:limit on various programs? Like, say, openfiles, which limits the number
:of open descriptors, a limit which "programmers using the interface probably
:assume doesn't exist"?
Oh come on, you know very well that this differs in major ways. Don't
even try to equate an arbitrary libc-originated memory limit from an
OS limit. For one thing, the arbitrary limit you imposed in the first
patch doesn't even begin to take into account available resources on
the machine. It just slaps in a 'hey, lets limit ourselves to 16384
elements and who gives a damn whether the user or sysad wants to be able
to handle more' type of limitation into libc. That's just plain silly.
I'm sorry, but it is. For another thing, *NONE* of us like the limits
set by the operating system. We would love to get rid of them. Just
because limits exist is hardly an excuse to go slam more limits into
the system, especially arbitrary ones. It's that sort of thinking that
has resulted in many of the ridiculous limitations already in the sytem,
such as maximum path lengths, descriptors, socket buf sizes, stat
structure (file size, which required the syscall to be completely
redone), and so forth.
Users can hang themselves a billion different ways. I am not interested
in getting hung up by library calls that assume I'm an idiot and decide
whether I should be allowed to do something or not simply because it might
use a lot of memory. That's ridiculous.
-Matt
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200103190504.f2J540A03836>