Bug 145434
Summary: | dont descend does not stop descent | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | David W. Legg <dwlegg> |
Component: | samba | Assignee: | Simo Sorce <ssorce> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | samba-bugs-list |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-10-19 19:09:04 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
David W. Legg
2005-01-18 14:04:53 UTC
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. |