Conference lassie::ucx

5425.0. "NFS problem with "updated" files" by UTRTSC::VWEE () Thu Apr 10 1997 03:44

Hello,

We got the following problem with NFS server (UCX 4.1 eco4).

A vms directory is exported, mounted on a digital UNIX host.
When a file is "updated", the changes where not seen on the unix host.
It takes about 10 minutes before you see the changes on the nfs client.
I used the following example.
$type a.a
1234567890
1234567890
1234567890
1234567890
1234567890
1234567890
1234567890

With the following dcl command procedure I changed the firts line.


$open/read/write infile a.a
$read infile record
$record ="aaaaaaaaaa"
$write/update infile record
$close infile
$exit

After running this procedure, on the the unix host I still see the old 
contents of the file. First line should be "aaaaaaaaaa" and is still
"12343567890" (for about 10 minutes.)

Is there someone who can explain this?
Is there a solution for this "problem"?

Thanks in advance

Gerard.


    

    Each time you reread the file from the client you reset the inactivity
    timer back to zero.  The inactivity timer control how long the file
    remains in the server's data cache.
    
    By default the inactivity timer is two minutes, so if you refrain from
    rereading for at least two minutes you will see any updates that have
    happened since the last time you read it.
    
    You can change the inactivity timer by editing the
    SYS$STARTUP:UCX$NFS_SERVER_STARTUP.COM file changing 
$ DEFINE/SYSTEM/EXE/NOLOG UCX$NFS00000000_INACTIVITY 02:00
    to the desired value.  Then restart the server.
    
    If you would like us to consider whether this behavior can be improved,
    please submit an IPMT.  Thanks.
    
    Julie

    
    Thanks for your answer, the customer changed this logical.
    It is working now.
    
    
    reagrds
    Gerard.