diff options
| author | Alexander Bokovoy <ab@samba.org> | 2008-01-17 16:51:14 +0300 |
|---|---|---|
| committer | Alexander Bokovoy <ab@samba.org> | 2008-01-17 16:59:29 +0300 |
| commit | 03387a0f5886d449eda359a5acecd830f3bd35bc (patch) | |
| tree | eff51ba251254ee3954f60b557ec4d1ff9aa553c /examples/VFS/skel_transparent.c | |
| parent | 026a66abecea3e3a54cdbfb97129d5e65608e5df (diff) | |
| download | samba-03387a0f5886d449eda359a5acecd830f3bd35bc.tar.gz samba-03387a0f5886d449eda359a5acecd830f3bd35bc.tar.bz2 samba-03387a0f5886d449eda359a5acecd830f3bd35bc.zip | |
Remove is_remotestorage() call from VFS. We already have statvfs() there to handle FS capabilities.
As discussed with Volker, it is better to calculate FS capabilities at
connection time. We already do this with help of VFS statvfs() call
which allows to fill-in system-specific attributes including FS
capabilities. So just re-use it if you want to represent additional
capabilities in your modules. The only caution is that you need to
call underlying statvfs() call to actually get system-specific
capabilities (and other fields) added. Then add module-specific ones.
(This used to be commit e342ca0d931f9a5c8ec9e472dc9c63f1fe012b3a)
Diffstat (limited to 'examples/VFS/skel_transparent.c')
| -rw-r--r-- | examples/VFS/skel_transparent.c | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/examples/VFS/skel_transparent.c b/examples/VFS/skel_transparent.c index 997783819c..f4cb9b15ba 100644 --- a/examples/VFS/skel_transparent.c +++ b/examples/VFS/skel_transparent.c @@ -681,7 +681,6 @@ static vfs_op_tuple skel_op_tuples[] = { /* offline operations */ {SMB_VFS_OP(skel_is_offline), SMB_VFS_OP_IS_OFFLINE, SMB_VFS_LAYER_TRANSPARENT}, {SMB_VFS_OP(skel_set_offline), SMB_VFS_OP_SET_OFFLINE, SMB_VFS_LAYER_TRANSPARENT}, - {SMB_VFS_OP(skel_is_remotestorage), SMB_VFS_OP_IS_REMOTESTORAGE, SMB_VFS_LAYER_TRANSPARENT}, {NULL, SMB_VFS_OP_NOOP, SMB_VFS_LAYER_NOOP} }; |