OS/2, eCS & ArcaOS - Technical > Networking

Updated Samba Client

<< < (43/46) > >>

David McKenna:
 Hi Steven,

  Thanks for the process dump guidance - it turns out smbd is not the problem...

  I originally installed SAMBA using the last Netlabs SAMBA WPI and it worked well. This has a utility - 'Simple SAMBA Configuration Center' that allows to update the basic SAMBA files from a zip file and I have done that with every drop from Paul up to now.

 To start SAMBA, the Netlabs 'smb.cmd' file starts smbd, nmbd, and winbindd from the Startup folder.

 After the latest drop, after the server froze, rebooted then renamed smb.cmd from the <alt>F1 menu command prompt. Then followed your instructions to capture a process dump, but there was no hang, and no file captured. Clients (OS/2 and Windows) could browse the share.

 Then started nmbd from another command prompt, and again there was no hang. Clients could browse.

 Then started winbindd from another command prompt and the server froze.

 So it appears winbindd is the culprit here...

Regards,

Paul Smedley:
interesting....I'll see if I can reproduce here....  I typically only start smbd.exe for my local testing...

David McKenna:
 Weirdly, if I try to run winbindd in a command prompt by itself (without first starting smbd or nmbd) I get a message that says it cannot be run in an OS/2 session...

Regards,

Paul Smedley:
interesting.... I haven't had a chance to investigate  yet, I've been fighting with binutils on the OS/2 side, and getting an additional binding added to the OpenHAB source on the non-OS/2 side - then of course there's that day job :)

Paul Smedley:
I seem to have fixed my binutils issue - just need to do some testing,  so then will try to get back onto the Samba issue...

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version