Red Hat Bugzilla – Bug 833407
Samba Change notification not recursive
Last modified: 2018-02-22 08:36:44 EST
I have opened bug 8901 against Samba due to change notification not being recursive.
I found a code change that works in our lab.
I would like to see this change integrated into an official RHEL5 version.
For reference : https://bugzilla.samba.org/show_bug.cgi?id=8901
We only integrate patches which are upstream. There is no upstream patch yet cause Volker wanted to see network traces to create a test to reproduce the problem and fix it correctly. We will be happy to integrate a correct upstream fix for the problem once it has been pushed upstream.
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release. Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products. This request is not yet committed for inclusion in
Samba 4.x introcuced a notifyd to improve change notifications. Change notifications are resurive as long as we operate on the SMB level. This means if a SMB client (CLI1) requests recursive change notifications and a second client (CLI2) does a change in a subdirectory, CLI1 will get a notification.
If CLI1 will not get a change notification if we operate on a file system level. This means if a local user changes a file in a subdirectory on the filesystem directly there will be no notification. The reason is that the kernel inotify is not recursive.
As explained, notifications are recursive on a samba share level. This means everything which happens on a share through SMB connections will trigger a notification.
It doesn't not work if someone modifies file directly on the file system Samba is running on. The reason for that is that the Kernel inotify support is not recursive. We can't fix that till the kernel adds support for this.