Your message dated Fri, 15 Apr 2005 13:54:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#110771: krb524d closes stderr, but continues to log to it
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; 31 Aug 2001 05:12:22 +0000
>From [EMAIL PROTECTED] Fri Aug 31 00:12:22 2001
Return-path: <[EMAIL PROTECTED]>
Received: from kuroneko.thok.org (kuroneko) [4.36.43.85]
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 15cgbO-0006Lq-00; Fri, 31 Aug 2001 00:12:22 -0500
Received: by kuroneko (Postfix, from userid 3382)
id 4B32B15093; Fri, 31 Aug 2001 01:12:21 -0400 (EDT)
From: "Mark W. Eichin" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: krb524d closes stderr, but continues to log to it
Full-Name: "Mark W. Eichin"
Message-Id: <[EMAIL PROTECTED]>
Date: Fri, 31 Aug 2001 01:12:21 -0400 (EDT)
Delivered-To: [EMAIL PROTECTED]
package: krb5-kdc
version: 1.2.2-6
daemon(3) on debian:
int daemon (int nochdir, int noclose);
Unless the argument noclose is non-zero, daemon() will
redirect standard input, standard output and standard
error to /dev/null.
com_err(3) says:
DESCRIPTION
Com_err displays an error message on the standard error
stream stderr (see stdio(3S)) ...
src/krb524/krb524d.c:158:
if (!nofork && daemon(0, 0)) {
com_err(whoami, errno, "while detaching from tty");
cleanup_and_exit(1, context);
}
yet com_err is still used to emit errors (which vanish into the
bitbucket):
write(2, "krb524d", 7) = 7
write(2, ": ", 2) = 2
write(2, "Bad encryption type", 19) = 19
write(2, " ", 1) = 1
write(2, "handling packet", 15) = 15
write(2, "\r", 1) = 1
write(2, "\n", 1) = 1
COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
krb524d 21909 root 2u CHR 1,3 156587 /dev/null
libkadm5 has krb5_klog_init, which does
if (do_com_err)
(void) set_com_err_hook(klog_com_err_proc);
and klog_com_err_proc uses syslog. Something similar should probably
be done in krb524d...
---------------------------------------
Received: (at 110771-done) by bugs.debian.org; 15 Apr 2005 20:54:12 +0000
>From [EMAIL PROTECTED] Fri Apr 15 13:54:12 2005
Return-path: <[EMAIL PROTECTED]>
Received: from smtp2.stanford.edu [171.67.16.125]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DMXpM-00058V-00; Fri, 15 Apr 2005 13:54:12 -0700
Received: from windlord.stanford.edu (windlord.Stanford.EDU [171.64.19.147])
by smtp2.Stanford.EDU (8.12.11/8.12.11) with SMTP id j3FKsBgS031583
for <[EMAIL PROTECTED]>; Fri, 15 Apr 2005 13:54:12 -0700
Received: (qmail 32417 invoked by uid 1000); 15 Apr 2005 20:54:11 -0000
To: [EMAIL PROTECTED]
Subject: Re: Bug#110771: krb524d closes stderr, but continues to log to it
From: Russ Allbery <[EMAIL PROTECTED]>
Organization: The Eyrie
Date: Fri, 15 Apr 2005 13:54:11 -0700
Message-ID: <[EMAIL PROTECTED]>
User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4 (Jumbo Shrimp, linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
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-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
This is in reference to Debian bug #110771 that you filed a little less
than four years ago.
The change that you suggested, to call set_com_err_hook in krb524d to
direct error messages to syslog appropriately, was made upstream and is
present in the current version of krb524d in sid and sarge. This problem
should be fixed.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
