Custom Query (292 matches)

I have SAMBA server 3.3.16-eCS 1.1.4-804 running. When I use the new client 2.2.0 beta4, I can copy files only as long as the target does not already exist. Here is an example where the r drive is a share on the server as seen by a client computer running 2.2.0 beta 4:

[r:\temp]dir *.txt

Volume in drive R is EVFS Directory of R:\temp\*.txt

2-07-14 16:52 5,624 124 foo.txt 2-07-14 16:52 5,624 0 pci_dump.txt

11,248 bytes in 2 files and 0 dirs 65,534 bytes allocated

1,616,200,556,544 bytes (1,505GB) free

[r:\temp]copy foo.txt foo2.txt R:\temp\foo.txt => R:\temp\foo2.txt

1 file copied

[r:\temp]copy foo.txt foo2.txt R:\temp\foo.txt => R:\temp\foo2.txt The segment is in use by another process. "R:\temp\foo2.txt"

0 files copied

[r:\temp]

I see the same problem with SAMBA client 2.1.5 GA.

In this file: ​ftp://ftp.netlabs.org/pub/samba/client/ndpsmb-2_2_0-beta3-20131004.zip

In README.TXT

5. Debugging

To produce a logfile please add an empty file called ndpsmb.dbg into the root drive."

However, client\src\debug.c

strncat(debugfile, getenv("ETC"), 2); strncat(debugfile, "
", sizeof(debugfile) - strlen(debugfile)

-1);

strncat(debugfile, "ndpsmb.dbg", sizeof(debugfile) -

strlen(debugfile) -1);

is the file around? if not we have no debug if (stat(debugfile, &filestat) !=0)

return;

Translating to English, the code is looking in %ETC for ndpsmb.dbg, not the "root drive".

​ftp://ftp.netlabs.org/pub/samba/client/ndpsmb-2_2_0-Beta3-20131004.wpi

WarpIn? will not begin installation, giving the subject message.