For example, i have some file on local windows system: ------- Create: aug 10 2009., 13:24:52 Change: aug 10 2009, 13:24:52 Open: may 20 2010, 17:31:32 ------- And then i open it, make some changes and close it. So: ------- Create: aug 10 2009, 13:24:52 Change: oct 7 2010, 12:31:51 Open: may 20 2010, 17:31:32 ------ changed only the date of the modification. This is right. And now i open samba share. Take some file: ----- Create: sep 3 2010, 14:42:25 Change: sep 3 2010, 14:42:25 Open: sep 8 2010 г., 0:12:54 ----- I open it, make NO changes and close it: ----- Create: oct 7 2010, 12:31:00 Change: oct 7 2010, 12:31:00 Open: oct 7 2010, 12:31:03 ----- As you can see all the parameters have changed! That`s wrong! my smb.conf -----smb.conf------------- [global] protocol = NT1 passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . obey pam restrictions = yes winbind enable local accounts = no passwd program = /usr/bin/passwd %u allow hosts = 192.0.2.0/24 dns proxy = no netbios name = fileserver browseable = no printing = bsd workgroup = NON debug level = 3 os level = 5 security = user max log size = 1000 log file = /var/log/samba/log.%m smb passwd file = /etc/smbpasswd load printers = no interfaces = 127.0.0.0/8 eth0 map to guest = bad user winbind trusted domains only = yes encrypt passwords = true passdb backend = tdbsam server string = Fileserver unix password sync = yes comment = Directorie syslog = 0 create mode = 0775 preferred master = no panic action = /usr/share/samba/panic-action %d bind interfaces only = yes pam password change = yes dos filetimes = yes dos filemode = yes [buh] recycle:touch = yes vfs objects = recycle browseable = yes writeable = yes path = /home/own/data-buh recycle:exclude = *.tmp,*.temp,*.~??,*.log recycle:keeptree = yes comment = Users valid users = User1, User2, User3,...,Administrator create mode = 0777 recycle:repository = .recycle/%U recycle:versions = yes directory mode = 777 allow hosts = 192.0.2.0/24 -----smb.conf-------------
*** This bug has been marked as a duplicate of bug 7725 ***