[OpenAFS] win 1.5.12 shell extension problem

Jeffrey Altman jaltman@secure-endpoints.com
Fri, 15 Dec 2006 14:51:30 -0500

Lars Schimmer wrote:
> Jeffrey Altman wrote:
>> You are sure this problem was not present in 1.5.11?
>> The reason I ask is because there have been no changes to the
>> pioctl or shell extension code in quite some time.
> I am 100% sure it wasn=B4t present in 1.5.10.
> And I know I updated a few PCs with 1.5.11 and got no problems told by
> our customers.
> They noticed the problem just after the upgrade to 1.5.12 (I updated
> some other software beside, doesn=B4t make it easier).
> So the problematic change could happend after 1.5.10 but wasn=B4t trapp=
> on the PCs with 1.5.11 in our department.
> I could try to test it tomorrow, but til yet I don=B4t have access to a
> user account on which that happens (I have to wait for monday to be
> really sure).
> MfG,
> Lars Schimmer

The last change to the pioctl and AFS Shell Extension code took place
in 1.5.8.  The change that was made was the implementation of a test
to determine if the AFS Client Service was running before attempting
to perform a pioctl call to the AFS Client for the purpose of
determining whether or not the path is associated with an AFS cell.

This change was made in order to ensure that long timeouts do not
occur on non-folders when the AFS Client Service is disabled.

Jeffrey Altman