Samba 2.2.1 released.

[Gerald Carter]

On Wed, 11 Jul 2001, Mike Black wrote:

> Mine behaves differently
>
> Original file (NT4):
> Created: Monday, July 17, 2000 12:01:53 PM
> Modified: Monday, July 17, 2000 12:01:53 PM
> Accessed: Monday, July 17, 2000 12:01:53 PM
>
> Copy to local (NT4):
> Created: Wednesday, July 11, 2001 8:49:05 AM
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Modified: Monday, July 17, 2000 12:01:53 PM
> Accessed: Monday, July 17, 2000 12:01:53 PM
>
> Copy to samba-2.0.7 (Linux)
> Created: Monday, July 17, 2000 12:01:53 PM
> Modified: Monday, July 17, 2000 12:01:53 PM
> Accessed: Wednesday, July 11, 2001 8:50:42 AM
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> Copy to samba-2.2.1 (Linux)
> Created: Monday, July 17, 2000 12:01:53 PM
> Modified: Monday, July 17, 2000 12:01:53 PM
> Accessed: Monday, July 17, 2000 12:01:53 PM
>
> This is the bug I reported -- ALL the date/times on samba-2.2.1 are
> being set to the current date/time because of the cache flush
> occurring AFTER the setftime routine.  Maybe Solaris behaves
> differently on the cache flush?

I am thoroughly confused now, because the mtime/actime for the 2.2.1
copy are the same as the original file on NT4.  It looks like 2.0.7
was messed up.  And why did NT reset the creation date on the local
copy?






jerry
 ---------------------------------------------------------------------
 http://www.valinux.com/     VA Linux Systems      gcarter at valinux.com
 http://www.samba.org/          SAMBA Team             jerry at samba.org
 http://www.plainjoe.org/                           jerry at plainjoe.org
 --"I never saved anything for the swim back." Ethan Hawk in Gattaca--