Hello,
I have a client with a windows utility that relies on "touch"ing
(changing
the mod time) on zero-length files in a folder for the purpose of judging
when that folder was last accessed. This works fine for him on mapped
windows servers, and from the local disk, but from a Samba (v3.0.22) volume,
the mod time doesn't change unless there was an actual data change within
the file. (ie, clicking "save" in notepad doesn't change the mod
time
unless he enters some data first.). I know this seems pretty trivial, but
it seems to make all the difference for some backup and SCADA software
packages.
Any ideas what I could do to fix this?
This is what the smb.conf looks like:
[global]
security = user
netbios name = Server1
server string = Server1
workgroup = WG
comment = File Server
os level = 1
create mode = 771
force create mode = 771
directory mode = 771
force directory mode = 771
force user = administrator
force group = users
map to guest = Bad User
null passwords = Yes
passdb backend = tdbsam, smbpasswd
case sensitive = No
username map = /etc/samba/smbusers
template shell = /bin/bash
dont descend = /proc,/dev,/etc,/usr
winbind cache time = 10
log level = 1
max log size = 2000
[Public]
writeable = yes
only user = yes
write list = @Public
path = /home/users/Public
comment = Public Share
valid users = @Public
user = @Public
Thank you!
Carlos Knowlton
On Thu, Jun 21, 2007 at 03:50:51PM -0500, Carlos Knowlton wrote:> Hello, > > I have a client with a windows utility that relies on "touch"ing (changing > the mod time) on zero-length files in a folder for the purpose of judging > when that folder was last accessed. This works fine for him on mapped > windows servers, and from the local disk, but from a Samba (v3.0.22) volume, > the mod time doesn't change unless there was an actual data change within > the file. (ie, clicking "save" in notepad doesn't change the mod time > unless he enters some data first.). I know this seems pretty trivial, but > it seems to make all the difference for some backup and SCADA software > packages. > > Any ideas what I could do to fix this?Can you test against 3.0.25a (or soon b) to see if this is currently a problem please ? Thanks, Jeremy.
Hello,
I have a client with a windows utility that relies on "touch"ing
(changing the mod time) on zero-length files in a folder for the purpose
of judging when that folder was last accessed. This works fine for him
on mapped windows servers, and from the local disk, but from a Samba
(v3.0.22) volume, the mod time doesn't change unless there was an actual
data change within the file. (ie, clicking "save" in notepad
doesn't
change the mod time unless he enters some data first.). I know this
seems pretty trivial, but it seems to make all the difference for some
backup and SCADA software packages.
Any ideas what I could do to fix this?
This is what the smb.conf looks like:
[global]
security = user
netbios name = Server1
server string = Server1
workgroup = WG
comment = File Server
os level = 1
create mode = 771
force create mode = 771
directory mode = 771
force directory mode = 771
force user = administrator
force group = users
map to guest = Bad User
null passwords = Yes
passdb backend = tdbsam, smbpasswd
case sensitive = No
username map = /etc/samba/smbusers
template shell = /bin/bash
dont descend = /proc,/dev,/etc,/usr
winbind cache time = 10
log level = 1
max log size = 2000
[Public]
writeable = yes
only user = yes
write list = @Public
path = /home/users/Public
comment = Public Share
valid users = @Public
user = @Public
Thank you!
Carlos Knowlton
PS, I'm not on the list, so please CC my return address in your
response, thanks!
Hey Guys, I have also noticed this problem; we have a ftp server with samba on it. I was trying to use find with mtime to remove folders older then 6 months. However when a folder is moved through a samba share the date stamp stays the same. This causes issues as old folders that want to be kept are moved; however the date stamp still remains the same. Is this going to be fixed in 3.2.0? Cheers, Adrian S.>From: "Carlos Knowlton" <carlosknowlton@gmail.com> >To: "Jeremy Allison" <jra@samba.org> >CC: samba@lists.samba.org >Subject: Re: [Samba] modification time inconsistency >Date: Wed, 11 Jul 2007 09:45:11 -0500 >On 6/21/07, Jeremy Allison <jra@samba.org> wrote: >> >>On Thu, Jun 21, 2007 at 03:50:51PM -0500, Carlos Knowlton wrote: >> > Hello, >> > >> > I have a client with a windows utility that relies on "touch"ing >>(changing >> > the mod time) on zero-length files in a folder for the purpose of >>judging >> > when that folder was last accessed. This works fine for him on mapped >> > windows servers, and from the local disk, but from a Samba (v3.0.22) >>volume, >> > the mod time doesn't change unless there was an actual data change >>within >> > the file. (ie, clicking "save" in notepad doesn't change the mod time >> > unless he enters some data first.). I know this seems pretty trivial, >>but >> > it seems to make all the difference for some backup and SCADA software >> > packages. >> > >> > Any ideas what I could do to fix this? >> >>Can you test against 3.0.25a (or soon b) to see if this is >>currently a problem please ? >> >>Thanks, >> >> Jeremy. >> > >Sorry for the delay in getting back to you on this. > >I have checked the latest Samba version, and the same behavior I saw in >3.0.22 also exists in 3.0.25b. Any ideas what might be happening, or how >to >fix this? > >Thanks, >Carlos >_________________________________________________________________ Movie session times on Messenger - add Movie Scout today! http://ninemsn.com.au/share/redir/adTrack.asp?mode=click&clientID=785&referral=hotmailtagline0707&URL=http://www.yourmovies.com.au/messenger/signup/