You experience a delay before the list of new files is returned when you run the DIR command or the LS command after you upgrade to Windows Services for UNIX 3.0 or to Windows Services for UNIX 3.5

Article ID: 894071 - View products that this article applies to.
Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986
(http://support.microsoft.com/kb/256986/ )
Description of the Microsoft Windows Registry
Expand all | Collapse all

SYMPTOMS

After you upgrade Microsoft Windows Services for UNIX 2.0 either to Microsoft Windows Services for UNIX 3.0 or to Microsoft Windows Services for UNIX 3.5, you experience a delay before the list of new files or of new folders is returned when you run the DIR command or the LS command.

For example, this problem occurs when you follow these steps:
  1. You mount a network file system (NFS) share using Client for NFS.
  2. You change the drive to the mounted NFS share.
  3. You run the DIR command on the mounted NFS share.
  4. In UNIX, you copy new files to the NFS share that you mounted in step 1.
  5. You repeat the DIR command until the new files are listed.

    Note It may take 20 to 30 seconds before the new files are listed.
Back to the top | Give Feedback

CAUSE

This problem occurs because Client for NFS caches the folder contents of the NFS share for a default time of 30 seconds.
Back to the top | Give Feedback

WORKAROUND

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To work around this problem, create a registry entry that controls the default time before the cache is invalidated. To do this, follow these steps:
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\Software\Microsoft\Client for NFS\CurrentVersion\Users\Default
  3. On the Edit menu, point to New, and then click Key.
  4. Type Cache, and then press ENTER.
  5. Locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\Software\Microsoft\Client for NFS\CurrentVersion\Users\Default\Cache
  6. On the Edit menu, point to New, and then click DWORD Value.
  7. Type AttributeTimeDelta, and then press ENTER.
  8. Right-click AttributeTimeDelta, and then click Modify.
  9. In the Edit DWORD Value dialog box, click Decimal, type a value that is less than the default value of 30 seconds, and then click OK.
  10. On the File menu, click Exit.
Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the top | Give Feedback

MORE INFORMATION

For more information about Windows Services for UNIX 3.5, visit the following Microsoft Web site:
http://technet.microsoft.com/en-us/interopmigration/bb380242.aspx
(http://technet.microsoft.com/en-us/interopmigration/bb380242.aspx)
Back to the top | Give Feedback

Properties

Article ID: 894071 - Last Review: November 15, 2005 - Revision: 1.2
APPLIES TO
  • Microsoft Windows Services for UNIX 3.5
  • Microsoft Windows Services for UNIX 3.0 Standard Edition
Keywords: 
kbtshoot kbprb kbinfo KB894071
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top