Control: clone -1 -2
Control: retitle -2 smbd No way to bind to IPv4 only
Control: severity -2 wishlist
Control: reopen -2
Control: tags -2 confirmed upstrea
Le jeu. 25 juil. 2019 à 01:36, Dark Penguin a écrit :
>
> On 24/07/19 22:14, Mathieu Parent wrote:
> > Le mer. 24 juil. 2019 à 00:27, Dark
On 24/07/19 22:14, Mathieu Parent wrote:
> Le mer. 24 juil. 2019 à 00:27, Dark Penguin a écrit :
>>
>> On 24/07/19 00:15, Mathieu Parent wrote:
>>> Version: 2:4.9.5+dfsg-5
>>>
>>> I'm closing this bug with the version in buster.
>>>
>>> Le dim. 21 juil. 2019 à 21:45, Dark Penguin a
>>> écrit :
Le mer. 24 juil. 2019 à 00:27, Dark Penguin a écrit :
>
> On 24/07/19 00:15, Mathieu Parent wrote:
> > Version: 2:4.9.5+dfsg-5
> >
> > I'm closing this bug with the version in buster.
> >
> > Le dim. 21 juil. 2019 à 21:45, Dark Penguin a
> > écrit :
> >>
> >> I tried this just now. The result
I tried this just now. The result is, basically, nothing: my kernel does
not have IPv6 support anyway, so restricting IPv6 out on the systemd
level does not change anything. There are still error messages about
being unable to bind to IPv6 upon restarting smbd, however with this,
restarting it
Le dim. 14 juil. 2019 à 15:09, Dark Penguin a écrit :
>
> This particular case could be less of a problem (at least to me) if
> adding "bind interfaces only = yes" was not the only way to disable IPv6
> in samba.
>
> Would it make sense to change the priority of an error message on
> startup
5 matches
Mail list logo