Darwin, Samuel writes:
So, for the problem to occur, one must make the changes to the file from
Windows, across the samba share, as well as be observing the file from
Windows Explorer.
We have encountered similar (bot not identical) problems and they were
solved by setting
csc policy =
The csc policy = disable did not seem to affect the issue.
-Original Message-
From: Roel van Meer [mailto:ro...@bokxing.nl]
Sent: Monday, May 10, 2010 2:33 AM
To: Darwin, Samuel
Cc: samba@lists.samba.org
Subject: Re: [Samba] non-windows behavior of samba
Darwin, Samuel writes:
So
-
From: John Drescher [mailto:dresche...@gmail.com]
Sent: Thursday, May 06, 2010 11:46 AM
To: Darwin, Samuel
Cc: samba@lists.samba.org
Subject: Re: [Samba] non-windows behavior of samba
On Wed, May 5, 2010 at 4:56 PM, Darwin, Samuel darw...@thirteen.org wrote:
We have a vendor who is going
By the way, I have isolated the problem to a subset of cases.
To review the problem case again briefly: mount Z: drive from Windows.
Actively modify a file. The Windows Explorer doesn't update
things like file size or modification date.
This is only broken when the modification happens
That should really work. I have several Samba servers with Windows XP
clients and with all of them client-made changes are immediately
reflected in Windows Explorer.
Apparently the smb.conf setting fam change notify = yes represents the
default value
fam change notify? From version
We have a vendor who is going to install an application server, and it
requires samba to behave as much like windows as possible. There is a
particular case they are complaining about.
1. Run samba on redhat server
2. Map a drive from windows. Let's say the Z: drive
3. Run a script to
On Wed, May 5, 2010 at 4:56 PM, Darwin, Samuel darw...@thirteen.org wrote:
We have a vendor who is going to install an application server, and it
requires samba to behave as much like windows as possible. There is a
particular case they are complaining about.
1. Run samba on redhat server
