OS/2, eCS & ArcaOS - Technical > Networking

Samba Users and Groups

<< < (3/7) > >>

David McKenna:
Neil,

  That's what I've been doing for testing - stop the server, then just unzip over the old files, then restart the server. Keep a zipped backup of the old so you can easily unzip that over the new one if needed.

Regards,

Paul Smedley:

--- Quote from: David McKenna on January 19, 2024, 06:07:44 pm ---  That's what I've been doing for testing - stop the server, then just unzip over the old files, then restart the server. Keep a zipped backup of the old so you can easily unzip that over the new one if needed.

--- End quote ---

There are no reports of data loss with even the latest 4.18/4.19 "Alpha, or Beta" code -  just some things that may not work as expected :) The only way things are gonna get fixed is if people test things and report issues. I don't *need* a Samba Server  for personal use -  I already have an Ubuntu Server on my LAN - I'm working on this as  I still care about the future of  ArcaOS / OS/2 -  even though  my daily driver is a laptop running Ubuntu 23.10.

Neil Waldhauer:
Thanks Paul, for making the samba port. I'm looking forward to updating my samba here.

I copied the 4.18 files over my mostly working Samba Server Version 3.6.25 for OS/2 based systems 1.3.0 (Refresh) The smb.conf file is unchanged.

When I access a share with my ArcaOS 5.1 SMB client, I get two exceptq trap files from SMBD.EXE.

Paul Smedley:

--- Quote from: Neil Waldhauer on January 20, 2024, 05:53:30 pm ---Thanks Paul, for making the samba port. I'm looking forward to updating my samba here.

I copied the 4.18 files over my mostly working Samba Server Version 3.6.25 for OS/2 based systems 1.3.0 (Refresh) The smb.conf file is unchanged.

When I access a share with my ArcaOS 5.1 SMB client, I get two exceptq trap files from SMBD.EXE.

--- End quote ---

Well that's a new one! Server logs should probably be the best way to see what's happening. Actually, can you try first with https://smedley.id.au/tmp/samba-4.19.4-os2-20240110.zip ?  the TRP is a SIGABRT - possibly a failed Assertion that was fixed after  the initial 4.18.x build.

Neil Waldhauer:
I tried the 4.19 build you suggest, and the traps are gone, but there is no response for client or browsing. I can't authenticate with "Samba Users and Groups".

Looking at logs, most are 0 length, but two are not. I'm not sure what the logs are trying to tell me.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version