[15819] in Kerberos_V5_Development
krbcc32s.exe and Windows Scheduled Tasks
daemon@ATHENA.MIT.EDU (Douglas E. Engert)
Thu May 20 11:40:55 2010
Message-ID: <4BF557FD.9040602@anl.gov>
Date: Thu, 20 May 2010 10:40:45 -0500
From: "Douglas E. Engert" <deengert@anl.gov>
MIME-Version: 1.0
To: "'krbdev@mit.edu'" <krbdev@mit.edu>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
It appears that if any KfW command is used by a Scheduled task,
the command will start krbcc32s. But when the task finishes, the
krbcc32s continues to run. This is on Windows 2003 SP2 with KfW
2.6.5.20040917.
The commands being used in the task are ms2mit and aklog to use
the ticket obtained be the task to get an AFS token.
The KfW 3.2.2 source architecture.txt and implementation.txt say
the Auto-Termination feature was never added.
We are starting to test using kdestroy and the krbcc32s -k option
to kill the process after the aklog.
What should the behavior of krbcc32s be when the scheduled task
ends?
I assume windows sends some notification event to any processes
that are part of the task. Is krbcc32s.exe failing to respond
to the event?
Is this fixed in later versions? I don't see anything in the
3.2.2 release notes about this issue. Other then "In fact, you
generally should never have to kill krbcc32s."
--
Douglas E. Engert <DEEngert@anl.gov>
Argonne National Laboratory
9700 South Cass Avenue
Argonne, Illinois 60439
(630) 252-5444
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
