Samba 2.2.1 released.

Mike Black mblack at csihq.com
Wed Jul 11 12:54:50 GMT 2001


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 A

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?
________________________________________
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: "Jeremy Allison" <jeremy at valinux.com>
To: "scott" <samba-ntdom at ml.slittle.com>
Cc: <samba-ntdom at lists.samba.org>; <samba-technical at samba.org>;
<samba at samba.org>
Sent: Tuesday, July 10, 2001 8:23 PM
Subject: Re: Samba 2.2.1 released.


scott wrote:
>
> Viewed from W2K, the Created/Modified dates are both the true creation
date* of the file.  If I do a 'stat' on the file from the
> Linux server, the Modify date shows as the true creation date, and the
Change date is when I copied the file from W2K to Samba.
>
> The timestamps are getting created correctly, but aren't getting read back
correctly.
>
> *true creation date = when the author actually made it.
>
> - - - - - - - - - - - - - - - - - - - - -
>
> > 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


The problem is that the underlying UNIX filesystem
doesn't store the creation date.

Samba fakes this by looking at all dates available to
a file and setting the oldest one it can find as the
creation date (as this is most probably the earliest
date the file has been around).

Samba will mess up when a file is copied such that the
creation date is later than the modification date. Samba
can have no idea when the file really was created on a
POSIX filesystem so selects the earliest date to display.

Regards,

Jeremy Allison,
Samba TEam.
--
--------------------------------------------------------
Buying an operating system without source is like buying
a self-assembly Space Shuttle with no instructions.
--------------------------------------------------------





More information about the samba-technical mailing list