Ticket History #238: server_acl.c logs errors incorrectly

From bjaspan@MIT.EDU Mon Nov 25 18:00:15 1996
Received: from MIT.EDU (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.69.0.28]) by rt-11.MIT.EDU (8.7.5/8.7.3) with SMTP id SAA09613 for <bugs@RT-11.MIT.EDU>; Mon, 25 Nov 1996 18:00:14 -0500
Received: from THE-TICK.MIT.EDU by MIT.EDU with SMTP
id AA09524; Mon, 25 Nov 96 18:00:13 EST
Received: by the-tick.MIT.EDU (940816.SGI.8.6.9/4.7) id XAA14002; Mon, 25 Nov 1996 23:00:12 GMT
Message-Id: <199611252300.XAA14002@the-tick.MIT.EDU>
Date: Mon, 25 Nov 1996 23:00:12 GMT
From: bjaspan@MIT.EDU
Reply-To: bjaspan@MIT.EDU
To: krb5-bugs@MIT.EDU
Subject: server_acl.c logs errors incorrectly
X-Send-Pr-Version: 3.99

mit

System: IRIX the-tick 5.3 02091401 IP22 mips



The acl-parsing and processing code in lib/kadm5/srv/server_acl.c does
not use krb5_klog_syslog to log errors; instead, it uses com_err and
fprintf(stderr). The com_err calls at least show up in the correct
log location, although they are ugly. The fprintf messages do not
show up anywhere if kadmind backgrounds itself. Some of the messages
that are fprintf'ed include "Invalid acl operation letter" (or
whatever it says).

This is not a high-priority 1.0 bug.




State-Changed-From-To: open-closed
State-Changed-By: bjaspan
State-Changed-When: Tue Dec 3 15:16:06 1996
State-Changed-Why:

Fixed on main branch (not 1.0):

lib/kadm5/srv/ChangeLog
lib/kadm5/srv/server_acl.c