Date: 18 Jun 2001 02:57:57 +0200 From: Assar Westerlund <assar@freebsd.org> To: Jonathan Lemon <jlemon@flugsvamp.com> Cc: freebsd-audit@freebsd.org, jlemon@freebsd.org Subject: Re: GLOB_LIMIT vs GLOB_MAXPATH Message-ID: <5llmmqtxii.fsf@assaris.sics.se> In-Reply-To: Jonathan Lemon's message of "Sun, 17 Jun 2001 09:28:17 -0500" References: <5ld783cvnq.fsf@assaris.sics.se> <20010617092817.M68883@prism.flugsvamp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jonathan Lemon <jlemon@flugsvamp.com> writes: > I don't really care about the name. However, I'm not sure if they > are the same thing; GLOB_MAXPATH limits the number of returned paths > that glob(3) will return. Does GLOB_LIMIT do the same, or does it > limit the number of *bytes* that are returned? GLOB_LIMIT in NetBSD and OpenBSD limits the number of matches or returned paths, so I think they are the same thing. The difference is that in NetBSD/OpenBSD the limit is fixed and hence there is no way (as in FreeBSD) to set the limit at `n' matches. Hence my patch setting limit to a default value if `gl_matchc == 0'. The other issue is if we should leave GLOB_MAXPATH as an alias. After all, this functionality was included in 4.3. /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-audit" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5llmmqtxii.fsf>