sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2024-12-23 17:34:34 +03:00
Code
68a3576629
samba-mirror/source4/ntvfs
History
Andrew Bartlett 8bac96de82 ntvfs/python: Adjust to use of PY_SSIZE_T_CLEAN 
This changes the type used for # arguments to PyArg_ParseTuple

Signed-off-by: Andrew Bartlett <abartlet@samba.org>
Reviewed-by: Jelmer Vernooij <jelmer@samba.org>
2016-01-07 23:33:10 +01:00
..
cifs s4: tidy up vfs cifs in regards to using share_string_option 2014-02-24 17:17:03 +01:00
cifs_posix_cli s4: pass down a memory context when performing share_string_option, to allow substitutions 2014-02-20 10:11:00 +13:00
common notify: Add "dir" to notify_event 2014-12-09 04:12:09 +01:00
ipc s4:ntvfs/ipc: fix ipc_close() 2015-07-03 02:00:28 +02:00
nbench s4-ntvfs: Cast getpid() result to unsigned int for GNU/Solaris build 2013-03-15 10:38:36 -07:00
posix ntvfs/python: Adjust to use of PY_SSIZE_T_CLEAN 2016-01-07 23:33:10 +01:00
print s4:ntvfs: add '_fn' suffix to all ntvfs_ops function pointers 2012-06-13 11:03:15 +02:00
simple s4: pass down a memory context when performing share_string_option, to allow substitutions 2014-02-20 10:11:00 +13:00
smb2 s4:ntvfs/smb2: ifdef out unused code 2014-11-25 07:25:45 +01:00
sysdep notify: Add "dir" to notify_event 2014-12-09 04:12:09 +01:00
unixuid ntvfs: Add error debug statements for set_unix_security 2015-11-05 09:23:15 +01:00
ntvfs_base.c Revert making public of the samba-module library. 2011-12-03 08:36:30 +01:00
ntvfs_generic.c s4/ntvfs: support FS_SECTOR_SIZE_INFORMATION query-info 2015-03-18 18:57:21 +01:00
ntvfs_interface.c s4:ntvfs: add '_fn' suffix to all ntvfs_ops function pointers 2012-06-13 11:03:15 +02:00
ntvfs_util.c
ntvfs.h s4:ntvfs: add '_fn' suffix to all ntvfs_ops function pointers 2012-06-13 11:03:15 +02:00
README
wscript_build Introduce system MIT krb5 build with --with-system-mitkrb5 option. 2012-05-23 17:51:50 +03:00

README 

This is the base of the new NTVFS subsystem for Samba. The model for
NTVFS backends is quite different than for the older style VFS
backends, in particular:

- the NTVFS backends receive windows style file names, although they
  are in the unix charset (usually UTF8). This means the backend is
  responsible for mapping windows filename conventions to unix
  filename conventions if necessary

- the NTVFS backends are responsible for changing effective UID before
  calling any OS local filesystem operations (if needed). The
  become_*() functions are provided to make this easier.

- the NTVFS backends are responsible for resolving DFS paths

- each NTVFS backend handles either disk, printer or IPC$ shares,
  rather than one backend handling all types

- the entry points of the NTVFS backends correspond closely with basic
  SMB operations, wheres the old VFS was modelled directly on the
  POSIX filesystem interface.

- the NTVFS backends are responsible for all semantic mappings, such
  as mapping dos file attributes, ACLs, file ownership and file times