On Thu, Oct 21, 2010 at 07:50:12PM +0200, Benny Halevy wrote: > On 2010-10-19 15:32, Trond Myklebust wrote: > > This would require access, directory create, and delete permissions for > > the directory '<mountpoint>/', which is not always a given. > > Correct. But that's pretty easy to probe :) > > > Besides, what if the server reboots, and my clientid changes? > > By <client-id> I meant a unique identifier for the client, not necessarily > the nfsv4.x clientid. The client could just as well use its ip address > (to help admins deal with the aftermath in case the client goes away) and its > boot time, or even a random string. Like the current sillyrename, it'd help in some cases, but not all. The set of cases where it worked would be a little larger, but also a little harder to explain. There may be diminishing returns to trying to perfect this kind of workaround. With 4.1 almost actually ready time might be better spent there, as it offers the chance of a complete solution. --b. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
