| Re: fstat update [message #14156 is a reply to message #14089] |
Tue, 26 January 1999 00:00   |
Vapuser
Messages: 63
Registered: November 1998
|
Member |
|
|
ashmall@my-dejanews.com (Justin Ashmall) writes:
> Dear All,
> Has anyone had a problem like this?
> We have a widget prog that periodically checks a file for new data,
> it does this by monitoring the file size as returned by fstat. This
> usually works fine but we have found on some (network) drives fstat
> always returns the same value, namely the file size it first saw,
> even though the file is growing. The only fix we've found is to
> constantly close and re-open the file which is a rather inelegant,
> if not inefficient, solution. It doesn't appear to be a buffering
> problem since we can see the file size changing (across the network)
> using the command line or a file manager.
> Any suggestions?
> (We're using IDL 5.1.1 under NT4)
>
> Many thanks,
>
> Justin
I've seen this problem in a UNIX environment when running an IDL
routine on one machine that was querying the size of a file which
resided on a disk that was NFS mounted from another machine. I am
unfamiliar with NT, so I don't know if 'network disk' is a fair
analog of NFS. In this case it was a feature of the operating
system/NFS, the file size didn't change as frequently on the NFS
client, therefore fstat reported EOF correctly as far as it could
see. The work around was to run the program on the machine which
hosted (i.e. for which the disk was local) the disk containing the
file in question.
Hope this helps in some small way.
whd
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
