samba - Jan 2007 - Mac OSX doesn't retain file timestamp when copying to SAMBA share

Hi All,

I'm not sure what's causing this but every time I copy a file from one 
of the Macs (details below) to the Samba server the file timestamp is 
changed to the copy time rather than retaining the last modified time. 
Does anyone know what could be causing this?

Systems:
Mac OSX (versions 10.3.x -> 10.4.x)
Windows 2000 Professional
Solaris 10 running Samba 3.0.11
 
Tests...
Mac OSX  ->  Mac OSX  retains timestamp
Mac OSX  ->  W2K share retains timestamp
Mac OSX  ->  Solaris Samba share REPLACES timestamp with copy time
W2K -> Solaris Samba share retains timestamp

smb.conf
[global]
   workgroup = OTP
   server string = OTP Server
   security = share
   load printers = yes
   log file = /usr/local/samba/var/log.%m
   max log size = 50
   socket options = TCP_NODELAY
   dns proxy = no
[otpserver]
   comment = OTP Server
   browseable = no
   writable = yes
[printers]
   comment = All Printers
   path = /var/spool/samba
   browseable = no
   guest ok = no
   writable = no
   printable = yes
[otpdata]
   comment = OTP Data
   path = /otp/Shared
   guest ok = yes
   read only = no
   writable = yes
   public = yes
[ftpdata]
   comment = FTP Data
   path = /otp/user/guest
   guest ok = yes
   read only = no
   writable = yes
   public = yes


Regards,
Troy.

I had a similiar issue recently, also on Solaris.  I was running samba
3.0.14a.

The clients where Win XP but anyhow a programmer that uses a share
noticed one day that one of the timestamps of a file she was copying from
somewhere else lost its timestamp.  In general though we could copy files
over to the share and the timestamps would be retained fine.

After lots of experimentation I finally figured out the culprit was when
she was copying over top an existing file and she was not the owner of
the existing file.  She had permission to clobber over the file via her
group permission but in that specific case, clobbering over a file she
didn't
actually own, the file copied would get a fresh timestamp.

The first thing I did was try Samba 3.0.23d to see if perhaps
it was fixed in that version.  Lo and behold it was, the issue went away
immediately upon upgrading to 3.0.23d.

Tom Schaefer


On Tue, 16 Jan 2007 08:30:06 +1100
Troy Kenah <troy@spaceape.com.au> wrote:
> 
> Hi All,
> 
> I'm not sure what's causing this but every time I copy a file from
one
> of the Macs (details below) to the Samba server the file timestamp is 
> changed to the copy time rather than retaining the last modified time. 
> Does anyone know what could be causing this?
> 
> Systems:
> Mac OSX (versions 10.3.x -> 10.4.x)
> Windows 2000 Professional
> Solaris 10 running Samba 3.0.11
>  
> Tests...
> Mac OSX  ->  Mac OSX  retains timestamp
> Mac OSX  ->  W2K share retains timestamp
> Mac OSX  ->  Solaris Samba share REPLACES timestamp with copy time
> W2K -> Solaris Samba share retains timestamp
> 
> smb.conf
> [global]
>    workgroup = OTP
>    server string = OTP Server
>    security = share
>    load printers = yes
>    log file = /usr/local/samba/var/log.%m
>    max log size = 50
>    socket options = TCP_NODELAY
>    dns proxy = no
> [otpserver]
>    comment = OTP Server
>    browseable = no
>    writable = yes
> [printers]
>    comment = All Printers
>    path = /var/spool/samba
>    browseable = no
>    guest ok = no
>    writable = no
>    printable = yes
> [otpdata]
>    comment = OTP Data
>    path = /otp/Shared
>    guest ok = yes
>    read only = no
>    writable = yes
>    public = yes
> [ftpdata]
>    comment = FTP Data
>    path = /otp/user/guest
>    guest ok = yes
>    read only = no
>    writable = yes
>    public = yes
> 
> 
> Regards,
> Troy.
>  
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/listinfo/samba
>