Custom Query (292 matches)

Run the following REXX script on a Samba share:

/* REXX */
'@echo off'
do I = 128 to 255
    say I'_'d2x(I)'_'copies(d2c(I),4)
    'echo TEST >'I'_'d2x(I)'_'copies(d2c(I),4)
    if stream(I'_'d2x(I)'_'copies(d2c(I),4),'c','query exists') = "" then do
        say "Filename with "I" ("d2x(I)") in name could not be created properly!"
        'PAUSE'
    end
end

This script tries to create files with ASCII chars between 128 and 255 and check afterwards if the file could be created properly. It chokes on 244 (0xF4) and 245 (0xF5) and pretends to create the others normally.

Looking at the directory afterwards however, you will see that the high ASCII charecters in some filennames seem to have been changed into ASCII 127. 198-199, 207-216, 221-222, 224, 226-240, 242-243, 247, 249, 251-252.

The test was perform with current Samba server (3.0.34) and current ndpsmb.dll (1.5).

The same script runs normally run on a WSEB share via LAN Requester.

This was discovered when testing for Ticket #68

I have installed ​ftp://ftp.netlabs.org/incoming/samba-3.0.26a-os2-20070912-wpi-v5.wpi on the server and NDFS plus ​ftp://ftp.netlabs.org/incoming/ndpsmb-3.0.26a-20070912.ZIP on the client. Browsing the shared resources frequently hangs the client. This is more evident while browsing via WPS. When the client hangs, the WPS does not respond anymore for several seconds, or some minutes, or forever.

The logs are snapshot of the following situation: server (192.168.1.1) just started with log level 5. Resource (Q) mounted on client (192.168.1.11). Volume Q opened via WPS, then q:\programs\pronews.exe started (launch failed, btw). Resource unmounted, server switched off and logs copied. Another client exists (192.168.1.10) but has no resource mounted. The server has two network interface, if this is of any interest.

Any suggestion? In the beginning I thought this was a problem on the client side, but in previous experiments I have sometimes seen the server hogged with 99% CPU, so maybe it is instead a server problem...

Please ask if more information are needed! Bye Gabriele

If there is a smb.conf file that has the lock directory value set (the server installer does that), the alternative lock directory of the client (in samba\lock\client) is once again the same as the one from the server, which leads to problems if server an cleint are run on the same machine an client is started before server.