Right, I forgot that one. But the potential resolution is the same, allow a configurable "unsafe" mode. If you want the inode-only optimization and are willing to take on the resulting unpredictability of ns_returnfile, go right ahead. But the majority of developers who don't know or don't care will have a much safer experience.
Titi Ala'ilima Lead Architect MedTouch LLC 1100 Massachusetts Avenue Cambridge, MA 02138 617.621.8670 x309 > -----Original Message----- > From: AOLserver Discussion [mailto:[EMAIL PROTECTED] On > Behalf Of Rusty Brooks > Sent: Thursday, August 21, 2008 3:25 PM > To: AOLSERVER@LISTSERV.AOL.COM > Subject: Re: [AOLSERVER] Data "corruption" with fastpath caching > > I don't have any opinion on the fix, but I think the actual objection > to > using the filename in the fix is that this would cause hard links to > files, which are for all intents and purposes The Same File, to be > considered different files by fastpath. (Hard links have different > names, but the same inode) > > Rusty -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
