> Steven N. Hirsch wrote:
>
> > Interesting how the mtime of "FOO" jumps by +11-minutes from cat'ing three
> > bytes to it, eh?
> >
> > I hope this is of help. Do you suppose that having the system clock on
> > the server out of sync with the client (client lags by ~11 minutes) is
> > triggering this? If so, how can I keep them in sync? And, why would this
> > not cause similar problems against 2.0.32?
>
> Hi Steve,
> It appears the only remaining problem is that the timestamp isn't being
> set correctly with the touch command, and the sudden change in time
> reflects the timestamp update on the server instead of the client.
Hmmm. The mtime is still not getting transferred from source to target on
the 'cp -a' command. That's been my primary frustration with smbfs. When
I copy foo to bar, "bar" ends up with its create timestamp rather than the
original file's mtime.
>
> I've made some changes to try a different way of setting the timestamp
> under WfW and will post a patch shortly.
>
> Regards,
> Bill
>
>