On 04/07/2016 04:35 PM, Oleksandr Natalenko wrote: > > Also, Soumya pointed me to handles API (/usr/include/glusterfs/api/glfs- > handles.h). If I got it correctly, probably, it could be used instead of path- > based API for FUSE bridge? I have briefly looked at it, but the article about > NFS handles (again, supplied to me by Soumya) remains unread so far :). Does > handles API represend inode API you are talking about? No, handles are not inodes. > >> That just seems like a bug. There should be one. > > That is definitely the bug. /usr/include/glusterfs/api/glfs.h clearly defines > it: > > === > int glfs_truncate (glfs_t *fs, const char *path, off_t length) __THROW > GFAPI_PUBLIC(glfs_truncate, 3.4.0); > === > > But linking executable with a call to glfs_truncate() results in error: > > === > CMakeFiles/xglfs.dir/xglfs_truncate.c.o: In function `xglfs_truncate': > /home/pf/work/devel/own/xglfs/xglfs_truncate.c:31: undefined reference to > `glfs_truncate' > === > > The bug was discussed more than year ago [1], but it seems there is no > solution so far. > Oh, haha. Yes, that sounds like a bug with the header file. ;-) But an implementation would be useful too. -- Kaleb _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
