Date: Wed, 6 Apr 2011 09:14:47 +0200 From: Gary Jennejohn <gljennjohn@googlemail.com> To: freebsd-fs@freebsd.org Subject: Re: Knob to turn off _POSIX_NO_TRUNC Message-ID: <20110406091447.0205de17@ernst.jennejohn.org> In-Reply-To: <BANLkTi=rA9uSzbzX0fV-8pci=p=Pa6PO6A@mail.gmail.com> References: <20110405141631.GA78089@deviant.kiev.zoral.com.ua> <20110405172746.4a02fe42@ernst.jennejohn.org> <20110405154002.GD78089@deviant.kiev.zoral.com.ua> <20110405183104.2304d94e@ernst.jennejohn.org> <BANLkTi=rA9uSzbzX0fV-8pci=p=Pa6PO6A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 5 Apr 2011 13:06:46 -0400 Ryan Stone <rysto32@gmail.com> wrote: > On Tue, Apr 5, 2011 at 12:31 PM, Gary Jennejohn > <gljennjohn@googlemail.com> wrote: > > OK, but trimming to me as a native english speaker means returning ENAMETOOLONG > > rather than allowing names longer than NAME_MAX. That is, after all, what trimming > > means - cutting off. > > The two behaviours here are: > > lookup_trim == 1 -- filenames are silently truncated(i.e. trimmed) if > longer than NAME_MAX > lookup_trim == 0 -- filenames longer than NAME_MAX are rejected with > ENAMETOOLONG > > The name makes perfect sense to me, personally. After sending off this e-mail the penny dropped and I finally realized just exactly what the patch is doing. Obviously, the way the sysctl is being used is correct. So, sorry for the noise. -- Gary Jennejohn
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110406091447.0205de17>