Date: Sun, 17 Jun 2001 09:28:17 -0500 From: Jonathan Lemon <jlemon@flugsvamp.com> To: Assar Westerlund <assar@freebsd.org> Cc: freebsd-audit@freebsd.org, jlemon@freebsd.org Subject: Re: GLOB_LIMIT vs GLOB_MAXPATH Message-ID: <20010617092817.M68883@prism.flugsvamp.com> In-Reply-To: <5ld783cvnq.fsf@assaris.sics.se> References: <5ld783cvnq.fsf@assaris.sics.se>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jun 17, 2001 at 11:17:45AM +0200, Assar Westerlund wrote: > The GLOB_MAXPATH flag to glob(3) does the same thing as the GLOB_LIMIT > one in NetBSD and OpenBSD (except for the default limit). Since this > is mostly used by ftpd and has been in the tree for a short amount of > time, I think it makes sense to keep it compatible with the other > BSDs. Enclosed is a patch that does this. Comments? 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? If GLOB_LIMIT is a count of pathnames, then I have no objections to the change, otherwise things should stay the same. -- Jonathan 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?20010617092817.M68883>