On Tue, Feb 07, 2006 at 10:52:48AM +0300, Vladimir Stavrinov wrote:
> On Tue, Feb 07, 2006 at 06:40:10AM +0100, Christian Perrier wrote:
> > > Are you using security=server?
> Yes.
Then your bug is bug #346045, which is fixed in 3.0.21b-1.
--
Steve Langasek Give me a lever lo
On Tue, Feb 07, 2006 at 06:40:10AM +0100, Christian Perrier wrote:
> > Are you using security=server?
Yes.
> Also please check whether crashes are still happening with the
> version 3.0.21b-1 which is currently available from
> incoming.debian.org and will move to the archive in about 12
> hours
tags 351496 moreinfo
thanks
Quoting Steve Langasek ([EMAIL PROTECTED]):
> On Mon, Feb 06, 2006 at 04:12:49PM +0300, Vladimir Stavrinov wrote:
> > Package: samba
> > Version: 3.0.21a-4
> > Followup-For: Bug #351496
>
> > The same problem: samba segfault when client try connect to share from
> > Wi
On Mon, Feb 06, 2006 at 04:12:49PM +0300, Vladimir Stavrinov wrote:
> Package: samba
> Version: 3.0.21a-4
> Followup-For: Bug #351496
> The same problem: samba segfault when client try connect to share from
> Windows box.
Are you using security=server?
> What happen with samba? Some years ago it
Package: samba
Version: 3.0.21a-4
Followup-For: Bug #351496
The same problem: samba segfault when client try connect to share from
Windows box.
What happen with samba? Some years ago it was reliable, and now it quit
buggy. We see many bug reports with key word "segfault" that seems was fixed
but
5 matches
Mail list logo