Subject: bug#668 closed by Mark Hindley <[email-masked]> (Re: bug#668: new samba-package available for debian.)

From: "Devuan bug Tracking System" <[email-masked]>
Date: Mon, 30 May 2022 12:38:04 +0000

This is an automatic notification regarding your bug report
which was filed against the samba package:

#668: samba on chimaera:i386 fails for logging and sockets

It has been closed by Mark Hindley <[email-masked]>.

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Mark Hindley <[email-masked]> by
replying to this email.

-- 
668: https://bugs.devuan.org/cgi/bugreport.cgi?bug=668
Devuan Bug Tracking System
Contact [email-masked] with problems

Subject: Re: bug#668: new samba-package available for debian.
From: Mark Hindley <[email-masked]>
To: [email-masked]
Cc: [email-masked]
Date: Mon, 30 May 2022 13:35:03 +0100

Version: 4.13.13+dfsg-1~deb11u4

On Mon, May 30, 2022 at 01:29:52PM +0100, Mark Hindley wrote:
> On Mon, May 30, 2022 at 02:19:46PM +0200, [email-masked] wrote:
> > hi.
> > 
> > since yesterday there's a new samba-package available for debian:
> > 
> > http://ftp.debian.org/debian/pool/main/s/samba/samba_4.13.13+dfsg-1~deb11u4_i386.deb
> > 
> > it would be nice, if this can be merged into devuan-repository, soon.
> 
> For unforked packages (like this), it happens automatically and is already
> available in chimaera-proposed-updates[1].

Closing with version.

Mark

Subject: samba on chimaera:i386 fails for logging and sockets
From: [email-masked]
To: [email-masked]
Date: Mon, 7 Mar 2022 19:44:59 +0100

Package: samba
Version: 2:4.13.13+dfsg-1~deb11u3
Architecture: i386

we're successfully running samba 2:4.9.5+dfsg-5+deb10u3 in a container
with devuan beowulf since several months, but decides to migrate all
containers to chimaera, but this fails for several reasons.

1.
having "bind interfaces only = yes" in config, smbd errors out with
"INTERNAL ERROR: open_sockets_smbd()" and "open_sockets_smbd: No sockets
available to bind to"

deactivating this config-entry makes smbd start normally.

2.
having "log file = /var/log/samba/%m.log" in config is completly
ignored. No such files are written, even when setting /varlog/samba to
mode 1777 and having parent dirs all at least at mode 751

further tests are stopped for now, because we need the system working,
but it seems, that the performance on network was worse than before
during initial connects.

using the same config with beowulf-container and samba
2:4.9.5+dfsg-5+deb10u3 works fine. (fortunately we could switch back to
the old container easily). Anything else but the inner system of the
container are equal!

if there're any additional infos are needed we'll try to give them, any
certain tests with the buggy samba may take a bit time, because we can't
switch the container at every time, but have to wait for evening or
weekend, to really have equal conditions.

regards

d.