Bug#692196: Debian installer 7.0 beta 3 on sparc Ultra 2 fails

Package: installation-reports Boot method: boot cdrom with net install version of ISO for installer 7, beta 3, sparc Image version: http://cdimage.debian.org/cdimage/wheezy_di_beta3/sparc/iso-cd/debian-wheezy-DI-b3-sparc-netinst.iso Date: Nov 2, 2012 Machine: Sun Ultra 2 Processor: 2 x 400 M

Bug#606350: [Pkg-samba-maint] Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

I installed these packages from sid this morning, onto an otherwise squeeze based system: samba-common2:3.5.6~dfsg-4 samba-common-bin2:3.5.6~dfsg-4 libwbclient02:3.5.6~dfsg-4 winbind 2:3.5.6~dfsg-4 I c

Bug#606350: [Pkg-samba-maint] Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

On Mon, Jan 3, 2011 at 2:37 AM, Christian PERRIER wrote: > > Eh, that's really strange, but thanks for the detailed investigation. > > Could you check whether you still experience the bug with the > 3.5.6~dfsg-3 packages? I suppose this is indeed what you're doing > right now... > > I'm afraid the

Bug#606350: [Pkg-samba-maint] Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

On Wed, Dec 22, 2010 at 2:05 AM, Christian PERRIER wrote: > > > Did you have any chance to test the amd64 packages I poointed you to? > > This fix is a good candidate for squeeze but I would like to have > success reports before requesting a freeze exception to the release team. > I've tested the

Bug#606350: [Pkg-samba-maint] Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

On Thu, Dec 9, 2010 at 5:00 PM, Christian PERRIER wrote: > > Hello, > > On > http://people.debian.org/~bubulle/samba-test/, > you'll soon find > packages which you may want to try. I just applied the patch from > Samba's Bugzilla and recompiled the

Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

On Wed, Dec 8, 2010 at 5:53 PM, Russ Allbery wrote: > > Looks like a file descriptor leak in pam_winbind. I think saslauthd isn't > at fault here. > > I did a test today... I noticed the number of fds had grown overnight by 20 to 40 per process. I did a restart of winbind and looked at the fd

Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

On Wed, Dec 8, 2010 at 10:02 PM, Russ Allbery wrote: > > > I'll reassign it. I wanted to see if anyone disagreed with me first. :) > > -- > Russ Allbery (r...@debian.org) > > > > This might be the same as the samba bu

Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

On Wed, Dec 8, 2010 at 5:53 PM, Russ Allbery wrote: > D G Teed writes: > > > I also count 200 connections like this: > > > unix 3 [ ] STREAM CONNECTED 39854981 > > /var/run/samba/winbindd_privileged/pipe > > > Most users are s

Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

On Wed, Dec 8, 2010 at 4:23 PM, Dan White wrote: > On 08/12/10 15:33 -0400, D G Teed wrote: > >> Here is what one of the directories looked like: >> >> ls -l 15950/fd >> >> total 0 >> lrwx-- 1 root root 64 Dec 8 13:52 0 -> /dev/null >> lr

Bug#394821: Proprietary driver from Matrox resolved the problem

A user at DebianHelp.org suggested I try the Matrox driver from Matrox. Earlier I did a compile from Debian sources at sarge1 release level and it did not resolve the problem. I worked in vesa mode for a couple of days before installing the Matrox proprietary driver, which resolves the issue fo

Bug#394821: mga_drv unresolved symbols after 4.3.0.dfsg.1-14sarge2 upgrade

Package: xserver-xfree86 Version: 4.3.0.dfsg.1-14sarge2 I have a G400 that was working fine in the most previous release (sarge1?) of xfree86 group of packages in Debian 3.1 stable. On the first reboot following the upgrade to 4.3.0.dfsg.1-14sarge2 of the series of related xfree86 packages, X re