search for: gvfsbackendsmb

...:14PM -0700, Jeremy Allison via samba wrote: > > Looking around inside that source code I also see: > > do_read (GVfsBackend *backend, > GVfsJobRead *job, > GVfsBackendHandle handle, > char *buffer, > gsize bytes_requested) > { > GVfsBackendSmb *op_backend = G_VFS_BACKEND_SMB (backend); > ssize_t res; > smbc_read_fn smbc_read; > > /* libsmbclient limits blocksize to (64*1024)-2 for Windows servers, > * let's do the same here to achieve reasonable performance. (#588391) > * > * TODO: port to pull me...

On Thu, 27 Oct 2016 16:57:13 -0700, Jeremy Allison <jra at samba.org> wrote : > On Fri, Oct 28, 2016 at 01:42:35AM +0200, Saint Germain via samba > wrote: > > On Thu, 27 Oct 2016 16:27:05 -0700, Jeremy Allison <jra at samba.org> > > > if you see any of these then it happened. > > > > Ok I understand how to check that it happened, but how can I make

...2:57AM +0200, Saint Germain via samba wrote: > > On linux, most current utilities like Nautilus (gvfs) still use SMB1 to > connect, so there is no chance to trigger a server-side copy. Oh, just checked the current gvfs source code to copy an smb file. It does: static gboolean copy_file (GVfsBackendSmb *backend, GVfsJob *job, const char *from_uri, const char *to_uri) { SMBCFILE *from_file, *to_file; char buffer[4096]; size_t buffer_size; ssize_t res; char *p; gboolean succeeded; smbc_open_fn smbc_open; smbc_read_fn smbc_read; smbc_write_fn smbc_w...

...Linux clients defaulting to SMB1 (via gvfsd-smb) while Windows happily negotiates SMB2 with the servers. If I restrict the servers to SMB2, gvfs can't connect, while smbclient on the console works fine if I pass -mSMB2. I can't see anything in https://git.gnome.org/browse/gvfs/tree/daemon/gvfsbackendsmb.c that would restrict the protocol version, either. Any ideas? Thanks, Adam

...nd inside that source code I also see: >>> >>> do_read (GVfsBackend *backend, >>> GVfsJobRead *job, >>> GVfsBackendHandle handle, >>> char *buffer, >>> gsize bytes_requested) >>> { >>> GVfsBackendSmb *op_backend = G_VFS_BACKEND_SMB (backend); >>> ssize_t res; >>> smbc_read_fn smbc_read; >>> >>> /* libsmbclient limits blocksize to (64*1024)-2 for Windows >>> servers, >>> * let's do the same here to achieve reasonable performa...

...> > > Looking around inside that source code I also see: > > > > do_read (GVfsBackend *backend, > > GVfsJobRead *job, > > GVfsBackendHandle handle, > > char *buffer, > > gsize bytes_requested) > > { > > GVfsBackendSmb *op_backend = G_VFS_BACKEND_SMB (backend); > > ssize_t res; > > smbc_read_fn smbc_read; > > > > /* libsmbclient limits blocksize to (64*1024)-2 for Windows > > servers, > > * let's do the same here to achieve reasonable performance. > > (#5883...

...gt; >>> > >>> do_read (GVfsBackend *backend, > >>> GVfsJobRead *job, > >>> GVfsBackendHandle handle, > >>> char *buffer, > >>> gsize bytes_requested) > >>> { > >>> GVfsBackendSmb *op_backend = G_VFS_BACKEND_SMB (backend); > >>> ssize_t res; > >>> smbc_read_fn smbc_read; > >>> > >>> /* libsmbclient limits blocksize to (64*1024)-2 for Windows > >>> servers, > >>> * let's do the same here...

...gt;>> do_read (GVfsBackend *backend, >>>>> GVfsJobRead *job, >>>>> GVfsBackendHandle handle, >>>>> char *buffer, >>>>> gsize bytes_requested) >>>>> { >>>>> GVfsBackendSmb *op_backend = G_VFS_BACKEND_SMB (backend); >>>>> ssize_t res; >>>>> smbc_read_fn smbc_read; >>>>> >>>>> /* libsmbclient limits blocksize to (64*1024)-2 for Windows >>>>> servers, >>>>> * let...