Your message dated Thu, 9 Jan 2003 07:37:50 +1100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#175283: libc6: getutent(3) messes with alarm clock
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; 4 Jan 2003 11:25:39 +0000
>From [EMAIL PROTECTED] Sat Jan 04 05:25:38 2003
Return-path: <[EMAIL PROTECTED]>
Received: from eriador.apana.org.au [203.14.152.116] (mail)
        by master.debian.org with esmtp (Exim 3.12 1 (Debian))
        id 18UmQo-0005fH-00; Sat, 04 Jan 2003 05:25:38 -0600
Received: from gondolin.me.apana.org.au ([192.168.0.6] ident=mail)
        by eriador.apana.org.au with esmtp (Exim 3.35 #1 (Debian))
        id 18UmQQ-0004aH-00
        for <[EMAIL PROTECTED]>; Sat, 04 Jan 2003 22:25:10 +1100
Received: from herbert by gondolin.me.apana.org.au with local (Exim 3.36 #1 (Debian))
        id 18UmQP-00023U-00
        for <[EMAIL PROTECTED]>; Sat, 04 Jan 2003 22:25:09 +1100
From: <[EMAIL PROTECTED]>
Subject: libc6: getutent(3) messes with alarm clock
To: [EMAIL PROTECTED]
X-Mailer: bug 3.3.10.2
Message-Id: <[EMAIL PROTECTED]>
Date: Sat, 04 Jan 2003 22:25:09 +1100
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=0.3 required=5.0
        tests=NO_REAL_NAME,SPAM_PHRASE_00_01
        version=2.41
X-Spam-Level: 

Package: libc6
Version: 2.2.5-14.3
Severity: normal

Calling getutent(3) from an application which uses alarm(2) causes the
latter's alarm clock to be overridden.

-- System Information
Debian Release: testing/unstable
Kernel Version: Linux gondolin 2.4.20-686-smp #2 SMP Sun Dec 1 13:37:59 EST 2002 i686 
Pentium III (Coppermine) GenuineIntel GNU/Linux

Versions of the packages libc6 depends on:
ii  libdb1-compat  2.1.3-7        The Berkeley database routines [glibc 2.0/2.

---------------------------------------
Received: (at 175283-done) by bugs.debian.org; 8 Jan 2003 20:38:16 +0000
>From [EMAIL PROTECTED] Wed Jan 08 14:38:16 2003
Return-path: <[EMAIL PROTECTED]>
Received: from goliath.apana.org.au [202.12.88.44] (mail)
        by master.debian.org with esmtp (Exim 3.12 1 (Debian))
        id 18WMxp-0001Kj-00; Wed, 08 Jan 2003 14:38:14 -0600
Received: from pelargir.apana.org.au ([203.14.152.113] helo=gondolin.me.apana.org.au)
        by goliath.apana.org.au with esmtp (Exim 3.35 #1 (Debian))
        id 18WMxT-0004xd-00; Thu, 09 Jan 2003 07:37:51 +1100
Received: from herbert by gondolin.me.apana.org.au with local (Exim 3.36 #1 (Debian))
        id 18WMxS-0000Gg-00; Thu, 09 Jan 2003 07:37:50 +1100
Date: Thu, 9 Jan 2003 07:37:50 +1100
To: Philip Blundell <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Subject: Re: Bug#175283: libc6: getutent(3) messes with alarm clock
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.4i
From: Herbert Xu <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-12.5 required=5.0
        tests=IN_REP_TO,REFERENCES,SIGNATURE_SHORT_DENSE,
              SPAM_PHRASE_00_01,USER_AGENT,USER_AGENT_MUTT
        version=2.41
X-Spam-Level: 

On Wed, Jan 08, 2003 at 11:47:59AM +0000, Philip Blundell wrote:
> Do you have a testcase that demonstrates this problem?

Sorry, glibc is correct, it was tcp-wrappers that was stuffing it up.
-- 
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email:  Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt


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

Reply via email to