I can reproduce this, but not every time. So a race condition might be involved.
Where does Samba log errors when it can't bind to a socket?
/var/log/samba/log.smbd:
[2010/03/18 10:06:11, 0] smbd/server.c:1069(main)
smbd version 3.4.7 started.
Copyright Andrew Tridgell and the Samba Team 199
On Thu, Mar 18, 2010 at 8:40 AM, Christian PERRIER wrote:
> Sid and, of course (well, I am one of the maintainers! So would be a
> shame if I don't run the right version of our package), 3.4.7.
I was using testing, not sid.
Olaf
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debi
Quoting Olaf van der Spek (olafvds...@gmail.com):
> On Wed, Mar 17, 2010 at 4:58 PM, Christian PERRIER wrote:
> > tags 574283 unreproducible
> > severity 574283 normal
> > thanks
>
> Why is it bugs get closed and severities altered without even a
> response from me?
Because I couldn't reproduce
On Wed, Mar 17, 2010 at 4:58 PM, Christian PERRIER wrote:
> tags 574283 unreproducible
> severity 574283 normal
> thanks
Why is it bugs get closed and severities altered without even a
response from me?
> Well:
>
> r...@mykerinos:~# sudo netstat -nlp|grep mbd
> tcp 0 0 0.0.0.0:445
tags 574283 unreproducible
severity 574283 normal
thanks
Quoting Olaf van der Spek (olafvds...@gmail.com):
> Package: samba
> Version: 2:3.4.7~dfsg-1
> Severity: serious
> Justification: IPv4 is kinda required
>
> Hi,
>
> Samba binds only to IPv6 and not to IPv4. I think this breaks stuff.
Wel
5 matches
Mail list logo
