16
Networking / Re: Updated Samba Client
« on: February 04, 2024, 03:24:06 am »Unfortunately I have no real clue why this is happening.Client 20240127 seems to work fine...
...re-tried here and still getting a TRAP-D.
OS2World.com Forum is back !!!
Remember to visit OS2World at:
http://www.os2world.com
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Unfortunately I have no real clue why this is happening.Client 20240127 seems to work fine...
...re-tried here and still getting a TRAP-D.
Just tried again with the 20240131 client version you list (also checked md5sum), and when I drag and drop from a local drive to the shared drive, the copied file has a truncated 8.3 style name on the share - does it every time. Hadn't tried before, but when doing it from a command line it works correctly. Strange it doesn't happen for you...I used WPS Move command - drag/drop is too hard in Virtualbox. For interest, can you try with ndpsmb-20240127.zip ? the only difference is the return code of the check for A.+,;=[].B
Hey Paul,
Thanks for that update - WINBINDD is now fine again and the lock files are deleted when the server is stopped just like before.
One weird thing I just noticed - when I copy a file to the server (from an OS/2 client - both 4.19) the file name is truncated to 8.3 format. Do you see that? I tried both EA's on and off, but still the same. I know this didn't used to happen, but not sure when it crept in (first noticed in the 20240202 drop).
EDIT: I backlevelled the ndpsmb.dll on the client to the 20240110 version, and now files are copied with the full name. So it's not the server, it's the 20240131 client plugin causing this.
Like Neil, I also don't see shares with the ArcaMapper browser (AN 5.1). Is there something that can be added to smb.conf to allow displaying shares? SMBTREE works fine (once the password is added).
One question - the 4.11 version of smbcl411 came with some binaries of things like net.exe and smbtree.exe etc. that were considerably smaller than the ones that come with the server. Is it OK to replace the old ones on the client with the new ones from the server package?
Network browsing is still not working, same as before.
I'm having trouble with this one - get a trap in WINBINDD.EXE at start. Logs attached. Went back to previous and all is well...Interesting. There were no *intentional* changes for winbindd - I'll have to figure out how to use it. You backlevelled just winbindd.exe?
I didn't detect any regressions on the server side. The latest build of smbd, samba-4.19.4-os2-20240202.zip, shares files here, just like the previous build. Network browsing is still not working, same as before.
Paul, here is Uniaud testlog, I hope that is what you are looking for.
Additional information: I tried to switch the devices mit the unimix command and the parameters on, each line said it had success, but in fact it does not switch the devices on. The remain silent.
@PaulQuoteI have no idea what the NOLARGENTEXEICON setting does and there is definitely no code in Samba that would handle it
From REXX T&T:Code: [Select]SET NOLARGENTEXEICON=n
Limit the number of megabytes (=n) the WPS should scan through Windows EXE files for the program icon before assigning a default icon
Available: New kernels from testcase (APAR PJ27886)
Source: XWorkplace Mailinglist
What has changed in the plugin is the code at https://github.com/psmedley/ndpsmb/blob/samba-4.19.x/src/ndpsmb.c#L1008 where if the WPS is testing A.+,;=[].B, we return immediately rather than calling smbwrp_getattr()While this certainly is a performance benefit, I think this approach just 'cures' a symptom but does not address it's root cause. Obviously, smbwrp_getattr() has a memory leak. Just checking for a specific name doesn't prevent the same problem resurfacing in other situations.
It's like the whole EXE has to be read in order for ANY info to actually show.