I'd say you were fortunate ;-)
> Others on the list have commented that all SMB servers reflect a zero file
> size until after close. This tends to support my guess that we're seeing
> a race with the kernel inode ageing.
I checked with the Win NT server here, and it appears to update the file
size as the writing progresses. After each write call smbfs refreshes
the inode, so assuming that the server returns the correct size, the
inode is up-to-date when the writing finishes. But if server is
reporting size 0 for each refresh, as it appears to be doing under Win
3.1, then we need to get the correct size before the file can be read.
Regards,
Bill