Daniel O'Connor wrote:
They were modifying the file on the unix side "behind Samba's back" so of course the caching was a problem. I'm not sure why it didn't show up in XP systems though.
Since your hosting this on BSD, which, to the best of my knowledge, doesn't support kernel oplocks, you probably *really* want to disable those if files are being modified in such a way. There's much potential for all kinds of things to go horribly wrong otherwise.
oplocks = no should do it. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
