Conference noted::pwv50ift

4238.0. "Directory Replication Limit (1000 files) V5" by GIDDAY::argus.stl.dec.com::Harkness () Tue Apr 01 1997 21:52

Hello all,

I have a question from a customer that I did not know how to answer.
Has anyone worked on this type of problem before...?

Does someone know how to overcome the Pathworks V5 directory replication
limit of 1000 files in a directory (short of upgrading to Pathworks V6)?

We have a large network with many subnets supporting a single Windows 
NT (lanmanager 3.0) domain. The Subnet containing the Primary Domain 
controller (Windows NT) also contains several Pathworks V5 
(Digital Unix V3.2C) servers. Some run other critical applications such 
as ORACLE which would entail a large (unacceptable) downtime to upgrade 
to UNIX V4.0 & PATHWORKS V6.

The problem is that when 1000 files is reached in an import directory, file
replication stops. (Yes 1000 files! including 1 file for each user's 
customized network connections). Replication will not recommence until the
export file count drops below 1000 files and files are removed from the 
import directory on the server (to fall below the 1000 file limit).

I have found references to many implementations of LANMANAGER 2.2 servers 
having this limit (search Microsoft's Knowledge base on the Web - Q115391, 
point 20). Does anyone know why?

Windows NT and Pathworks V6.0 don't have this problem.

Does anyone have any ideas on how to resolve this problem?

We are currently contemplating turning off netlogon on the PATHWORKS servers
during logon hours (creating user password update delays of up to one day 
on the PATHWORKS servers).


Any input would be helpfull,


Greg Harkness
Sydney CSC

    once again... the OpenVMS V5 server does not do replication at all.
    If you mean the UNIX server, try these commands
    
    extract/nohead 4238
    delete 4238.0
    add entry ranger::pwosf
    open pwosf
    write
    (then read in your extracted text)