[24495] in Kerberos
Re: Memory Leak problems with krb5_get_init_creds_password?
daemon@ATHENA.MIT.EDU (brian.joh@comcast.net)
Tue Aug 23 10:38:15 2005
From: brian.joh@comcast.net
To: Ken Raeburn <raeburn@mit.edu>, Sam Hartman <hartmans@mit.edu>
Date: Tue, 23 Aug 2005 14:36:02 +0000
Message-Id: <082320051436.9696.430B3452000E1A0A000025E02200734840080106D2020E079D0D@comcast.net>
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 8bit
cc: kerberos@mit.edu
Errors-To: kerberos-bounces@mit.edu
Yeah, I wasn't sure what the standard practice is, and whether
it was necessary to keep calling res_ninit() multiple times per
context. I suggested that route because it is more conservative.
It keeps all the functionality the same, while reducing the leak.
Res_ninit() is supposed to read the DNS config files, and it
was my *impression* that most applications want to always
have the latest DNS config. For example, if you change
your name servers in /etc/resolv.conf, my *impression* was
most running applications will "see" the new name servers
with a restart. MIT and Heimdal currently do this.
Brian
-------------- Original message --------------
> Yes, I think allocating the storage and initializing it at most once
> per context, delayed until the actual resolver usage, is the right
> way to deal with this. Simply adding a pointer field to the context,
> initialized to NULL, is probably the way to start....
>
> Ken
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
