Your message dated Mon, 05 Dec 2005 22:02:07 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#342104: fixed in kfreebsd-5 5.4-9
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 5 Dec 2005 11:51:34 +0000
>From [EMAIL PROTECTED] Mon Dec 05 03:51:34 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mail.t-systems.cz ([212.67.76.249])
        by spohr.debian.org with esmtp (Exim 4.50)
        id 1EjEnS-0000rX-GL
        for [EMAIL PROTECTED]; Mon, 05 Dec 2005 03:46:18 -0800
Received: from mefisto.t-systems.cz (faust.t-systems.cz [10.246.110.12])
        by mail.t-systems.cz (Postfix) with ESMTP id 426408A313;
        Mon,  5 Dec 2005 12:46:11 +0100 (CET)
Received: from enigma ([10.246.109.32]) by mefisto.t-systems.cz with Microsoft 
SMTPSVC(6.0.3790.211);
         Mon, 5 Dec 2005 12:46:11 +0100
Date: Mon, 5 Dec 2005 12:46:10 +0100 (CET)
From: Petr Salinger <[EMAIL PROTECTED]>
X-X-Sender: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: strange mysql bug, possibly thread related
In-Reply-To: <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-OriginalArrivalTime: 05 Dec 2005 11:46:11.0147 (UTC) 
FILETIME=[7CEDF1B0:01C5F991]
X-T-Systems_Czech-MailScanner: Found to be clean
X-T-Systems_Czech-MailScanner-SpamCheck: not spam (whitelisted),
        SpamAssassin (score=-5.88, required 5, autolearn=not spam,
        ALL_TRUSTED -3.30, AWL 0.02, BAYES_00 -2.60)
X-MailScanner-From: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02

Package: kfreebsd-5 
Version: 5.4-8

Hi.

> I've installed libc 2.3.1+kbsd.13 (alongside kfreebsd-image 5.4-8) 
> and mysql works ok. 
> Indeed, and amavis=>clamd works, too :)

I played with it and the reason seems related to 
thread signaling AND setuid()/setgid() calls.

Robin, Konstantinos, please, can you test to change 
user of mysql and clamd to root ?
After that, it should work with latest glibc.

Given it helps also for you:

There is a exception granted for SIGUSR1 and SIGUSR2,
but not for our current thread signals. 
Details in kernel sources, sys/kern/kern_prot.c, function 
int cr_cansignal(struct ucred *cred, struct proc *proc, int signum)

Already fixed in FreeBSD 6.0, suggested patch for package kfreebds-5:
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/kern/kern_prot.c.diff?r1=1.198&r2=1.187.2.3

Petr




---------------------------------------
Received: (at 342104-close) by bugs.debian.org; 6 Dec 2005 06:11:14 +0000
>From [EMAIL PROTECTED] Mon Dec 05 22:11:14 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 4.50)
        id 1EjVtv-000484-G9; Mon, 05 Dec 2005 22:02:07 -0800
From: Aurelien Jarno <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.60 $
Subject: Bug#342104: fixed in kfreebsd-5 5.4-9
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Mon, 05 Dec 2005 22:02:07 -0800
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-4.8 required=4.0 tests=BAYES_00,FROM_ENDS_IN_NUMS,
        HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2005_01_02

Source: kfreebsd-5
Source-Version: 5.4-9

We believe that the bug you reported is fixed in the latest version of
kfreebsd-5, which is due to be installed in the Debian FTP archive:

kfreebsd-5_5.4-9.diff.gz
  to pool/main/k/kfreebsd-5/kfreebsd-5_5.4-9.diff.gz
kfreebsd-5_5.4-9.dsc
  to pool/main/k/kfreebsd-5/kfreebsd-5_5.4-9.dsc
kfreebsd-source-5.4_5.4-9_all.deb
  to pool/main/k/kfreebsd-5/kfreebsd-source-5.4_5.4-9_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurelien Jarno <[EMAIL PROTECTED]> (supplier of updated kfreebsd-5 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Mon,  5 Dec 2005 19:18:13 +0100
Source: kfreebsd-5
Binary: kfreebsd-image-5.4-1-686 kfreebsd-image-5.4-1-586-smp 
kfreebsd-headers-5-686 kfreebsd-headers-5.4-1-686 kfreebsd-headers-5.4-1-586 
kfreebsd-headers-5.4-1-486 kfreebsd-image-5-586-smp kfreebsd-headers-5-686-smp 
kfreebsd-image-5.4-1-686-smp kfreebsd-headers-5.4-1-586-smp 
kfreebsd-headers-5-586 kfreebsd-headers-5-586-smp kfreebsd-image-5.4-1-486 
kfreebsd-headers-5.4-1-686-smp kfreebsd-image-5-686-smp kfreebsd-image-5-486 
kfreebsd-image-5-586 kfreebsd-headers-5-486 kfreebsd-source-5.4 
kfreebsd-image-5-686 kfreebsd-headers-5.4-1 kfreebsd-image-5.4-1-586
Architecture: source all
Version: 5.4-9
Distribution: unstable
Urgency: low
Maintainer: GNU/kFreeBSD Maintainers <debian-bsd@lists.debian.org>
Changed-By: Aurelien Jarno <[EMAIL PROTECTED]>
Description: 
 kfreebsd-source-5.4 - source code for kernel of FreeBSD 5.4 with Debian patches
Closes: 342104
Changes: 
 kfreebsd-5 (5.4-9) unstable; urgency=low
 .
   * Fix thread signaling with setuid()/setgid() calls for signals different
     than SIGUSR1 and SIGUSR2. Patch pulled from upstream (FreeBSD 6.0), thanks
     to Petr Salinger for the link (closes: bug#342104).
Files: 
 a03362ec86d945f66d1898816278a5ac 1443 devel optional kfreebsd-5_5.4-9.dsc
 74c139327c8986bb2de671d2c633b2f0 36279 devel optional kfreebsd-5_5.4-9.diff.gz
 b35da3a3deb0834503d93e4e757e2791 13136792 devel optional 
kfreebsd-source-5.4_5.4-9_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDlOqjw3ao2vG823MRAjUXAJ9/2A93OAo7BqoH1wzmD+RImEUfIgCffTRq
8T/ilhvEBDKkXnwiMHYz9Ec=
=buJN
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to