[15820] in Kerberos_V5_Development
Re: krbcc32s.exe and Windows Scheduled Tasks
daemon@ATHENA.MIT.EDU (Jeffrey Altman)
Thu May 20 15:45:36 2010
X-Envelope-From: jaltman@secure-endpoints.com
X-MDaemon-Deliver-To: krbdev@mit.edu
Message-ID: <4BF59159.8080708@secure-endpoints.com>
Date: Thu, 20 May 2010 15:45:29 -0400
From: Jeffrey Altman <jaltman@secure-endpoints.com>
MIME-Version: 1.0
To: krbdev@mit.edu
In-Reply-To: <4BF557FD.9040602@anl.gov>
Reply-To: jaltman@secure-endpoints.com
Content-Type: multipart/mixed; boundary="===============2121542255=="
Errors-To: krbdev-bounces@mit.edu
This is a cryptographically signed message in MIME format.
--===============2121542255==
Content-Type: multipart/signed; protocol="application/pkcs7-signature";
micalg=sha1; boundary="------------ms020407040304020109070209"
This is a cryptographically signed message in MIME format.
--------------ms020407040304020109070209
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
On 5/20/2010 11:40 AM, Douglas E. Engert wrote:
> 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.
>=20
> The commands being used in the task are ms2mit and aklog to use
> the ticket obtained be the task to get an AFS token.
>=20
> The KfW 3.2.2 source architecture.txt and implementation.txt say
> the Auto-Termination feature was never added.
>=20
> We are starting to test using kdestroy and the krbcc32s -k option
> to kill the process after the aklog.
>=20
> What should the behavior of krbcc32s be when the scheduled task
> ends?
>=20
> 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?
>=20
> 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."
>=20
Scheduled tasks are not part of a logon session. Therefore, there is no
logoff event to cause krbcc32s.exe to terminate. You must manually
terminate it as part of your task.
krbcc32s.exe -k
--------------ms020407040304020109070209--
--===============2121542255==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
--===============2121542255==--
