similar to: Documentation/Feature Clarification Request: Server Side Copy and VFS_FRUIT

There are two styles of SSC: - the "normal" protocol style called copy-chunk, where the copy is requested in IO ranges by the client and performed server-side - the Apple way enabled by fruit:copyfile where the client requests the *whole* file to be copied in one request to be performed by the server The problem with the latter is that for large file the copy takes some time and

These are a combination of "temp" and "real" files. The user is deleting/moving PDFs, InDesign and image files. I'm presuming hidden files are also getting deleted when the real files are. The filesystem has been solid (XFS) up until the switch to SMB. From: itdept_head <itdept_head at grown-up.com> To: Cc: "samba at lists.samba.org" <samba at

Hello Mike, I know from my customers that moving files under macOS Ventura on a SMB share is a mess and completely broken by Apple (e. g. moved files cannot be opened until you reconnect). Unfortunately I do not have a ZFS-backed machine to test against available right now to confirm the behaviour. Is your order of "vfs objects? correct? Regards, Alexander > On Thursday, Mar 02, 2023 at

Hi folks, I have a number of Mac users connecting to our Samba fileserver over VPN. When they copy/move files between shares it takes quite a long time due to our miserable business internet connection. I set fruit:copyfile = yes in smb.conf expecting that to enable server-side copy for Mac users. Unfortunately, it did not. Befuddled, I tried the same copy operation from a Windows VM and it

Is this supposed to be supported in Samba 4.7.1? Server side copies work fine using a Windows client. From mac OS 10.13.2, there's a full transfer of a file being copied. $ smbutil statshares -a ================================================================================================== SHARE ATTRIBUTE TYPE VALUE

On Fri, 17 Jan 2025 22:32:03 +0100 Carlos Alberto Balseiro Mayi via samba <samba at lists.samba.org> wrote: > ? > HI everyone. > > I've been analyzing a problem with an embedded Linux/FPGA device that > in some cases was failing to run properly when using files from a > samba share. After some time I've found it is related to Samba bug > 12783 and setting

I have a Cyber Power LE1000DG UPS I got from Best Buy this weekend. I plan to use it with a TrueNAS scale system, and it is connected via USB. Vendor link: https://www.cyberpowersystems.com/product/ups/battery-backup/le1000dg/. TrueNAS has you pick a UPS driver. I could not find any "LE" related models on https://networkupstools.org/stable-hcl.html (which is the list TrueNAS uses). Per

I have a Smart-UPS RT 3000 XL connected via serial cable to TrueNAS TrueNAS-9.2.1.2-RELEASE-x64 (002022c) which runs on FreeBSD 9.2-RELEASE-p3. When I start the NUT service, I get the message: Oct 20 01:53:50 truenas notifier: very old or unknown APC model, support will be limited Which I interpret as an indicator of less than optimal operating mode. I suspect that the model identifier is not

Greetings, I'm not sure what else to add. If you need more info please let me know. Any input is greatly appreciated. Eric On Sat, Mar 4, 2023 at 2:58?PM Eric <rvwbug at gmail.com> wrote: > Greetings, > > This is my first attempt at multi-site with unique subnets (actually > first attempt at more than on DC). > > I had the existing "defaultFirstSite"

Hi, Can anyone tell me why CopyFile is the only undefined reference from Path.cpp? --------------- llvm[2]: Linking Debug executable gccld c:/projects/build/MinGW/llvm-1-1/tools/gccld/Debug/gccld.o(.text+0x439): In function `Z15EmitShellScriptPPc': c:/projects/src/llvm-1/llvm/tools/gccld/gccld.cpp:127: undefined reference to `llvm::sys::CopyFile(llvm::sys::Path const&, llvm::sys::Path

But breaks VC++. The problem is, Windows.h defines "CopyFile" as a macro that's either "CopyFileA" or "CopyFileW". Path.h is included before Windows.h, so the declaration has the name "CopyFile" while the definition has "CopyFileA". Instant compilation error. Not sure what the best way to fix it is, but I'll check it in as soon as I

----- Quick summary: In the File:Open dialog, please change "S files (*.q)" to "S files (*.q, *.ssc, *.S)" and show the corresponding files (including .SSC and .s files). ----- Background This is motivated by the following query to R-help: >Date: Thu, 16 Mar 2006 22:44:11 -0600 >From: "xpRt.wannabe" <xprt.wannabe at gmail.com> >Subject: [R] Is

Really nice write-up on the Samba-based Open Source project ! https://arstechnica.com/gadgets/2020/07/an-easy-mode-for-zfs-we-test-the-truenas-core-12-0-beta/ Congratulations to the FreeNAS/TrueNAS folks ! Jeremy.

Hi Reid, The error still exists. However, looking on the function in Win32/Path.cpp: -------------- void sys::CopyFile(const sys::Path &Dest, const sys::Path &Src) { if (!::CopyFile(Src.c_str(), Dest.c_str(), false)) ThrowError("Can't copy '" + Src.toString() + "' to '" + Dest.toString() + "'"); } -------------- I

No, although its declared in the Path.h file, its actually not in the Path class. Have a look. Not sure why you're still seeing that problem. The same change to Unix/Path.cpp fixed the same problem on Cygwin and Linux. Reid. On Thu, 2004-12-23 at 15:48, Henrik Bach wrote: > Hi Reid, > > The error still exists. However, looking on the function in Win32/Path.cpp: > --------------

Dear all, Thanks to those of you who have replied, the majority of the comments pointed out that the error caused by scan may originate from another function, and closer inspection of the output from traceback() reveals that it is in fact the read.table function where the error is originating from the full output of which I have included below. The error msg I recieve is Error in

Hi Reid, Looking closer at the build process, I find that Path.cpp doesn't get compiled, even if it is a newer version than its *.o file. That's probaly the reason the error still exists. I've zipped and attached the trace after the point the new Path.cpp was updated by cvs. It clearly shows that it newer gets compiled and now shows that it is the dependencies in the makefile

? HI everyone. I've been analyzing a problem with an embedded Linux/FPGA device that in some cases was failing to run properly when using files from a samba share. After some time I've found it is related to Samba bug 12783 and setting kernel oplocks on global fix the issue. But while looking at that I have found a strange behavior I can't understand. I have guest ok = yes on the

Hello, Everyone. Now I have some spare time and I've decided to build LLVM on Mingw. I've grab the latest 1.7 release (not CVS snapshot). Here are some issues fixed during the build. Now I'm preparing gcc build. So, I think, there will some other "parts" 1. Prerequisites 1.1 GCC 3.4.5 from mingw.org site. $ gcc --version gcc.exe (GCC) 3.4.5 (mingw special) Copyright (C)

Hi Reid, Looking closer at the build process, I find that Path.cpp doesn't get compiled, even if it is a newer version than its *.o file. That's probaly the reason the error still exists. I've zipped and attached the trace after the point the new Path.cpp was updated by cvs. It clearly shows that it newer gets compiled and now shows that it is the dependencies in the makefile