Re: VxWorks memory error when closing ADA file

["Smark" <not.provided@all.com>]

"Jeff Creem" <jeff@thecreems.com> wrote in message
news:%LoF6.21500$bA2.5861739@typhoon.ne.mediaone.net...
>
> "Smark" <not.provided@all.com> wrote in message
> news:9c3vp5$f2s4@cui1.lmms.lmco.com...
> > "Jeff Creem" <jeff@thecreems.com> wrote in message
> > news:Wv2F6.20517$bA2.5461988@typhoon.ne.mediaone.net...
> > >
> > > vxWorks version? who's compiler? target type? host type? These might
> help...
> > >
> > > Some notes:
> > >
> > >  On vxWorks, if your file access is via FTP (unless you have a local
> disk or
> > > have
> > > specifically tried to make it via NFS it is probably via FTP). If it is
> ftp,
> > > the file is not written to
> > > the network until the file is closed.
> >
> > In fact, the same is true for file access via NFS.
> >
> > Mark
> >
>
> In fact unless they broke this for more recent versions of vxWorks, NFS did
> not cache
> the entire file in RAM prior to flushing it to the network nor does it read
> the entire file into
> RAM prior to allowing read calls to operate. If this is happening with your
> target I suspect a configuration
> problem.

Actually, we use NFS precisely for the reason you mention about reading --
we don't always want to read the entire file into memory.

Regarding writing, there is a variable in nfsDrv, called "nfsCacheSize," which
determines how much data is cached in memory before writing to the external
file.  So, really, neither of us were completely accurate above.  If
nfsCacheSize is set higher than the typical file size, the behavior I
described will occur; if it is lower, the behavior you described happens.

FWIW, there is also a "FIOSYNC" ioctl function in nfsDrv, which can be used to
explicitly flush data to the remote file.

Mark