Red Hat Bugzilla – Bug 145434
dont descend does not stop descent
Last modified: 2007-11-30 17:07:06 EST
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Description of problem: Have smb.conf that is otherwise working and includes the following lines: [data] browsable = yes path = /data ... dont descend = /data/aba/CGI Version-Release number of selected component (if applicable): samba 3.0.9-1.3E.2 How reproducible: Always Steps to Reproduce: 1. Set up smb.conf as above 2. service smb start 3. point NT explorer at data share 4. descend into /data/aba/CGI 5. should see nothing in CGI directory Actual Results: 6. Could see contents of CGI directory and below. Expected Results: Should have seen the CGI directory as an empty directory. Additional info: Tried dont descend = ./data/aba/CGI but this did not help.
CIFS (and Windows in general) does wierd things with mixed-case directories. I tried "dont descend = data/aba/cgi" and it worked as documented. Re-read the section on page 521 of the HOWTO and Reference Guid where it says "Note that Samba can be very fussy about the exact format of the "dont descend" entries. For example, you may need ./proc instead of just /proc. Experimentation is the best policy. :-)
I tried the path with both upper and lower case directory names. I tried it with and wihout the leading slash. I tried it with './' at the beginning. I even tried just naming the directory not to be descended, eg. 'CGI'. It only worked when I tried it with a top level directory, eg. /proc Multi-level paths, eg. /data/aba/CGI, just do not work.
REOPENED status has been deprecated. ASSIGNED with keyword of Reopened is preferred.
This bug is filed against RHEL 3, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you.