Re: [MLUG] samba access time question

[Sven <EMAIL:PROTECTED>]

> 
> I do not fully understand your problem as I have never messed with smb 
> timestamps before. Could this smb.conf option help?

It is about unix timestamps:
	atime (last access)
	mtime (last modify)
	ctime (create time)
The atime will be set on almost any access to the file (not to the i-note), 
i.e. ls, stat etc. will not change it, cat, tar, cp are accessing the file 
itself and thus change the atime!
A closer look at cp shows, the source will have only atime changed, the target 
has all times changed.
Windows >= 2k has the same timestamps (I don't know where, since fat32 does 
not support it, does it? Looks to me, as if ctime=mtime, atime=now)
If I now take a file from windows and copy it to the samba exported folder, 
all unix times are the same and set to the windows modified time. The ctime 
and mtime are fine for me, but atime should be the time of the access!

> 
>        dos filetimes (S)
>               Under DOS and Windows, if a user  can  write  to  a
>               file  they  can  change  the timestamp on it. Under
>               POSIX semantics, only the owner of the file or root
>               may  change  the  timestamp. By default, Samba runs
>               with POSIX semantics  and  refuses  to  change  the
>               timestamp  on  a file if the user smbd is acting on
>               behalf of is  not  the  file  owner.  Setting  this
>               option  to   yes allows DOS semantics and smbd will
>               change the file timestamp as DOS requires.
> 
>               Default: dos filetimes = no
> 
> Mark
Sorry, but it does not work. It sets atime and mtime to the windows modified 
time and ctime to the current date/time (how does that make sense?????)

/sven

_______________________________________________
members mailing list
EMAIL:PROTECTED
http://mlug.missouri.edu/mailman/listinfo/members