On 8/1/07, Josh Kelley <[EMAIL PROTECTED]> wrote: > On 7/31/07, Victor Cicero <[EMAIL PROTECTED]> wrote: > > Is this "modification timestamp" problem a known one? Or am I the > > first to experience it? If it is know, has it been fixed? If not > > fixed, is there a workaround I can use (short of working locally on > > the hard drive)? > > Samba has two timestamp options in smb.conf that are supposed to help > with this sort of problem: "dos filetime resolution" and "fake > directory create times". Have you tried enabling those options? > > Josh Kelley >
On 8/2/07, James R Grinter <[EMAIL PROTECTED]> wrote: > You may get some benefit from a later Samba. They've changed > the file timestamp resolution (to include more than just > to the nearest second) in later versions. > > James. > Josh and James, thank you for your tips. I first tried the "dos filetime resolution" option. It didn't help. I then updated my Samba installation from 3.0.21a to 3.0.23a (that's the most my Fedora Core 4 would allow using yum). That didn't help either. Any other ideas? Thanks, Victor -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
