scannedonly vfs module ported to samba 3.5

Volker Lendecke Volker.Lendecke at SerNet.DE
Sun Dec 13 05:23:18 MST 2009


On Fri, Dec 11, 2009 at 04:22:59PM +0100, Olivier Sessink wrote:
> Volker Lendecke wrote:
> > On Tue, Dec 08, 2009 at 03:47:53PM +0100, Olivier Sessink wrote:
> >> Thanks, implemented that.
> >>
> >> A last question (I think): I currently use a global static variable
> >> gsendbuffer which holds  filesnames that are to be sent to the virus
> >> scanner. This assumes that a single samba process works on one share
> >> (different share definitions might use different virus scanners).
> >>
> >> Is this assumption correct?
> > 
> > No, it is not. You might want to look at
> > SMB_VFS_HANDLE_[GS]ET_DATA and some sample uses in other
> > modules. I must admit these macros are old, ugly and need
> > to be replaced, but they are right now the preferred way to
> > have per-instance specific VFS data.
> 
> and the data field in the 'struct vfs_handle_struct' pointer that is
> passed to the connect function, is that a 'per share' structure?

It is a "per instance", i.e. "per connection to a share"
structure.

Volker
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20091213/493cf9f9/attachment.pgp>


More information about the samba-technical mailing list