[Nfs-ganesha-devel] Re: cb_program or cb_callback_ident always the same

This list has been deprecated. Please subscribe to the new devel list at lists.nfs-ganesha.org. Hi. The client program ID in a lock owner is an opaque. That is, it's not defined in the spec, and the server can't use it for anything other than a byte string. The concatenation of the client-ID and the opaque part of the lock owner is unique, but the opaque part of the lock owner itself is not. That value only has meaning to the client. Daniel On 04/30/2018 08:18 AM, Tuan Viet Nguyen wrote: > This list has been deprecated. Please subscribe to the new devel list at > lists.nfs-ganesha.org. > > > > Hello, > > While trying to get more information related to the lock owner, I'm > trying to get the client program id and realize that it always takes the > same value (easy to do with a test program forking another process, parent > lock a file range then the child locks another range). Is it something > similar to the client process id that is stored in the client record > structure? or any other suggestions? > > Thank you > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > > _______________________________________________ > Nfs-ganesha-devel mailing list > Nfs-ganesha-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel > > ------------------------------------------------------------ ------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Nfs-ganesha-devel mailing list Nfs-ganesha-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel