On Mon, 2024-12-16 at 09:33 +0300, Michael Tokarev wrote:
> If wouldn't know what to do with this issue either, if Andrew didn't
> step in.
Which is why I did. :-)
I'm sorry for the dismissive tone, I mostly wanted to provide that
clearly missing context, I totally agree we do need a better way
16.12.2024 01:49, Mrten wrote:
On 14/12/2024 04:13, Andrew Bartlett wrote:
If Samba has no interfaces to bind to, it will panic, which triggers a
backtrace, but this is intentional and controlled, not a segmentation fault.
OK, thank you for that. I think these systemd messages threw me off:
On 14/12/2024 04:13, Andrew Bartlett wrote:
If Samba has no interfaces to bind to, it will panic, which triggers a
backtrace, but this is intentional and controlled, not a segmentation fault.
OK, thank you for that. I think these systemd messages threw me off:
Dec 14 00:59:01 kyra systemd[1]:
If Samba has no interfaces to bind to, it will panic, which triggers a
backtrace, but this is intentional and controlled, not a segmentation
fault.
--
Andrew Bartlett (he/him) https://samba.org/~abartlet/
Samba Team Member (since 2001) https://samba.org
Samba Developer, Catalyst IT https://catalys
Package: samba
Version: 2:4.17.12+dfsg-0+deb12u1
Severity: normal
Dear Maintainer,
* What led up to the situation?
a reboot changed the name of the interface, then it took me a while
to notice that samba wasn't up.
when investigating, i discovered that a wrong interface name
segf
5 matches
Mail list logo
