Problems with times on files
David Schwarz
dave at deakin.edu.au
Tue Jul 10 23:03:44 GMT 2001
>Testing Samba 2.2.0 shows it is however doing what _you_ think it should
>- which is IMHO wrong - at least it is not how a normal copy is
>performed or how win2000 behaves taliking to another win2000 machine.
>For instance,
>Oringinal file (local Win200),
>Created: 12 June 2001 19:07:41
>Modified: 12 June 2001 19:07:42
>Accessed: 10 July 2001
>Copied to local drive
>Created: 10 July 2001 17:32:34
>Modified: 12 June 2001 19:07:42
>Accessed: 10 July 200
>Copied to Win2000 Share
>Created: 10 July 2001 17:32:51
>Modified: 12 June 2001 19:07:42
>Accessed: 10 July 200
>Copied to Samba 2.2.0 (Solaris 2.7) Share
>Created: 12 June 2001 19:07:42
>Modified: 12 June 2001 19:07:42
>Accessed: 10 July 200
>Moved to a Samba 2.2.0 (Solaris 2.7) Share
>Created: 12 June 2001 19:07:42
>Modified: 12 June 2001 19:07:42
>Accessed: 10 July 200
>So the move is correct but the copy is incorrect but the inverse of what
>Mike Black was reporting.
>Of course this was on a 2000 machine and solaris not NT4 and linux, but
>why would that cause it to do it the correct way ;-)
I am wondering if this is why we see long times for roaming profiles to
load and unload.
I am not sure how they work, but I guess it something to do with
comparing the
create time on the local computer and the server, and if they are
different recopying up or down
We many files transfering as the profile roams
Can anybody confirm this is what happens, if this is true, then having
the create time set incorrectly could have
a large impact on logon times.
Any feedback would be appreciated
Dave...
--
___________________________________________________________
David Schwarz
Desktop/Workgroup Section Leader
ITS, Deakin University
Ph (03) 52278938
Fax (03) 52278866
Email Dave at deakin.edu.au
___________________________________________________________
More information about the samba-technical
mailing list