On Tue, Mar 06, 2007 at 12:53:28PM +0100, Steinar H. Gunderson wrote:
> Anyhow, I can reproduce this in my side now. I'll try to figure out what's
> leaking...
It's a memory leak (or rather, two distinct memory leaks, but only one of
them really hurts) in libblkid; see #413661. (There's also a tin
On Mon, Mar 05, 2007 at 10:32:12PM -0300, Carlos Carvalho wrote:
> It's 188 lines long, here's a summary:
Whoa! :-)
Anyhow, I can reproduce this in my side now. I'll try to figure out what's
leaking...
/* Steinar */
--
Homepage: http://www.sesse.net/
--
To UNSUBSCRIBE, email to [EMAIL PROTEC
Steinar H. Gunderson ([EMAIL PROTECTED]) wrote on 6 March 2007 00:58:
>On Mon, Mar 05, 2007 at 08:46:04AM -0300, Carlos Carvalho wrote:
mountd is indeed no longer killed with signal 11 on startup for me,
>>> Wow, I never saw that error. I just had mysterious mount failures, and they
>>> di
On Mon, Mar 05, 2007 at 08:46:04AM -0300, Carlos Carvalho wrote:
>>> mountd is indeed no longer killed with signal 11 on startup for me,
>> Wow, I never saw that error. I just had mysterious mount failures, and they
>> disappeared completely in 1.0.12.
> The message is printed by grsec (it's a secu
On Sun, Mar 04, 2007 at 07:38:13PM -0300, Carlos Carvalho wrote:
> mountd is indeed no longer killed with signal 11 on startup for me,
Wow, I never saw that error. I just had mysterious mount failures, and they
disappeared completely in 1.0.12.
> however it's memory consumption grows without limi
Package: nfs-common
Version: 1:1.0.12-2
The changelog (for nfs-common, though it should be for
nfs-kernel-server...) says
nfs-utils (1:1.0.12-1) unstable; urgency=high
* New upstream release.
* Fixes mysterious mountd failure. (Closes: #412818)
mountd is indeed no longer killed with signa
6 matches
Mail list logo
