| Date: | Tue, 27 Mar 2007 17:06:06 -0700 (Pacific Daylight Time) |
| From: | petesea@bigfoot.com |
| Subject: | Kfw 3.2 alpha and multiple krbcc32s processes for a user |
| To: | kfw-bugs@mit.edu |
I posted the question below to the kerberos list on Feb 6 - Subject "KfW
3.1 and multiple krbcc32s.exe processes". I haven't had much opportunity
to dig into it further until now.
I came up with a simple way to test it and found the problem still exists
with KfW 3.2 alpha.
I created a new user (easier to test this way)... then created a
"Scheduled Task" that runs klist as this new user. The task was
configured to run every minute for 5 minutes or so.
It doesn't really matter if "klist" works or not, the goal is simply to
run something that starts krbcc32s.
Each time the scheduled task runs, a new krbcc32s process is created even
if one already exists for the user. The krbcc32s processes never die. I
used "Process Explorer" to monitor the processes which makes it very easy
to see when they are created and by who. Obviously, if you do something
like kinit every couple of hours 24/7 this becomes a problem.
Any chance this could be fixed for the 3.2 release?
On Tue, 6 Feb 2007, Jeffrey Altman wrote:
3.1 and multiple krbcc32s.exe processes". I haven't had much opportunity
to dig into it further until now.
I came up with a simple way to test it and found the problem still exists
with KfW 3.2 alpha.
I created a new user (easier to test this way)... then created a
"Scheduled Task" that runs klist as this new user. The task was
configured to run every minute for 5 minutes or so.
It doesn't really matter if "klist" works or not, the goal is simply to
run something that starts krbcc32s.
Each time the scheduled task runs, a new krbcc32s process is created even
if one already exists for the user. The krbcc32s processes never die. I
used "Process Explorer" to monitor the processes which makes it very easy
to see when they are created and by who. Obviously, if you do something
like kinit every couple of hours 24/7 this becomes a problem.
Any chance this could be fixed for the 3.2 release?
On Tue, 6 Feb 2007, Jeffrey Altman wrote:
Show quoted text
> petesea@bigfoot.com wrote:
>
> There is one krbcc32s.exe per login session. krbcc32s.exe runs until
> the session ends.
>
> krbcc32s.exe is the credential cache server. It runs when krb5_32.dll
> is loaded if it is not already started in the current session.
>
>> I have a user running some batch files as scheduled jobs (aka cron
>> jobs). He's noticed that after a period of time there will be several
>> krbcc32s.exe processes running which never go away.
>>
>> Under what conditions might this happen?
>>> jobs). He's noticed that after a period of time there will be several
>> krbcc32s.exe processes running which never go away.
>>
>> Under what conditions might this happen?
> There is one krbcc32s.exe per login session. krbcc32s.exe runs until
> the session ends.
>
>> The batch files run kinit -kt with a keytab/principal, then do what
>> they need to do, then run kdestroy. The NIM is never running (as far
>> as I know).
>>> they need to do, then run kdestroy. The NIM is never running (as far
>> as I know).
> krbcc32s.exe is the credential cache server. It runs when krb5_32.dll
> is loaded if it is not already started in the current session.