What is needed to address bug#1601, Excel and Powerpoint file timestamp changes?

[Jeremy Allison]

On Wed, Feb 02, 2005 at 05:06:43PM -0500, David Pullman wrote:

> I don't think so?  We have the default dos filetimes = no.  If I 
> understand smb.conf(5), setting this to yes lets anyone besides the 
> owner or root to change the timestamp.  The problem we're having that 
> everyone besides the owner is changing the timestamp _now_, even with 
> out that set to yes.  In other words, we already have too much time 
> stamp change.
> 
> It seems from empirical testing that the timestamp is not "reverting" as 
> it does on the W2K server tests when the file is closed with no changes.
> 
> Of course, with Windows it's hard to define what "no changes" means (ala 
> the Word file switcheroo thing).  But what we mean by no changes is open 
>  the file, look at it and then do a file close.  No edits.

But if a new file is created, or a deliberate write is done, then the mtime
*will* change. Now I found and fixed a bug for 3.0.11 where mtime changes made
by the client prior to a write need to be "sticky" (ie. restored on close).

This sounds like it will fix the problem exactly, so I'd strongly suggest
you try 3.0.11.

Jeremy.