With bug 44054 we optimized the blacklist handling for share paths. This causes the usability for the user to decrease enormously. Not knowing the blacklist path behaviour a customer creates a share beneath /var/share The share is now created in ldap, but not created in samba. So the share is not visible via windows. The message in the listener.log is a good hint, so now the recommended ucr variables can be set. That you have to restart listener is mentioned in the ucr variable. But doing this there still no share in windows visible. So you have to modify the share or rerun the listener module to make the share created completely. Setting a new path for the share is not enough to create the share. -------------------------------------------------------------------------- To make this handling more easy for the user we could consider, to show a hint in the UMC when the share is to be created in a blacklisted path. If the path is whitelisted, we may trigger the share creation in some way, or describe exactly the necessary steps.
*** Bug 50419 has been marked as a duplicate of this bug. ***
This may be two Bugs: 1. Maybe the directory should not be created when it is blacklisted anyway. 2. There is no feedback to the user in UMC. The first could be easy to fix. The second is a valid concern but may require some conceptual changes. I just closed Bug 50419 as a duplicate of this, but maybe we should fix the first point via that bug and handle the feedback issue on this one?
This issue has been filed against UCS 4.4. UCS 4.4 is out of general maintenance and components may have vastly changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.