Samba 2.2.1 released.
Mike Black
mblack at csihq.com
Fri Jul 13 11:24:02 GMT 2001
OK -- I repeated this and am using a file with an easier-to-spot date.
Also -- my testing before involved an NFS mount so I removed that variable.
Original
Created Thursday, November 19, 1998 12:47:48 AM
Modified Thursday, November 19, 1998 12:47:48 AM
Accessed Thursday, November 19, 1998 12:47:48 AM
Copy to local (NT4) (Move behaves the same too)
Created Thursday, July 12, 2001 5:34:31 AM
Modified Thursday, November 19, 1998 12:47:48 AM
Accessed Thursday, July 12, 2001 5:34:31 AM
Copy to share (NT4)
Created Thursday, July 12, 2001 5:35:47 AM
Modified Thursday, November 19, 1998 12:47:48 AM
Accessed Thursday, July 12, 2001 5:35:47 AM
Copy to share (Win2000)
Created Thursday, July 12, 2001 5:40:08 AM
Modified Thursday, November 19, 1998 12:47:48 AM
Accessed Thursday, July 12, 2001 5:40:08 AM
Copy to samba-2.0.7 (Linux)
Created Thursday, November 19, 1998 12:47:48 AM
Modified Thursday, November 19, 1998 12:47:48 AM
Accessed Thursday, July 12, 2001 5:41:30 AM
stat() results on file:
Change: Thu Jul 12 05:43:30 2001
Modify: Thu Nov 19 00:47:49 1998
Access: Thu Nov 19 00:47:49 1998
Copy to samba-2.2.1 (Linux)
Created Thursday, November 19, 1998 12:47:48 AM
Modified Thursday, November 19, 1998 12:47:48 AM
Accessed Thursday, November 19, 1998 12:47:48 AM
stat() results on file:
Change: Thu Jul 12 05:45:48 2001
Modify: Thu Nov 19 00:47:49 1998
Access: Thu Nov 19 00:47:49 1998
Looks like my original bug (21369) may have been addressed but now this is a
new one.
But showing all 3 as oldest date will screw up lots of things (like Source
Integrity -- RCS)
.
All the NT boxes behave the same -- Samba is deviant from NT.
I never had any problems with the old 2.0.7 behavior but I do see problems
with the
new behavior.
________________________________________
Michael D. Black Principal Engineer
mblack at csihq.com 321-676-2923,x203
http://www.csihq.com Computer Science Innovations
http://www.csihq.com/~mike My home page
FAX 321-676-2355
----- Original Message -----
From: "Gerald Carter" <gcarter at valinux.com>
To: "Mike Black" <mblack at csihq.com>
Cc: "Jeremy Allison" <jeremy at valinux.com>; "scott"
<samba-ntdom at ml.slittle.com>; <samba-ntdom at lists.samba.org>;
<samba-technical at samba.org>; <samba at samba.org>
Sent: Wednesday, July 11, 2001 1:33 PM
Subject: Re: Samba 2.2.1 released.
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--
More information about the samba-technical
mailing list