Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 639141

Summary: 'default case' parameter description in smb.conf(5) is confusing
Product: Red Hat Enterprise Linux 6 Reporter: Bryan Mason <bmason>
Component: sambaAssignee: Guenther Deschner <gdeschner>
Status: CLOSED ERRATA QA Contact: Ales Zelinka <azelinka>
Severity: low Docs Contact:
Priority: low    
Version: 6.0CC: azelinka, dpal, gdeschner, mishu
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: samba-3.5.4-78.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 480405 Environment:
Last Closed: 2011-05-19 13:14:26 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:
Bug Depends On: 480405    
Bug Blocks:    

Description Bryan Mason 2010-09-30 22:08:27 UTC
+++ This bug was initially created as a clone of Bug #480405 +++

Created attachment 329255 [details]
Proposed patch to reword description of "default case" in smb.conf(5)

Description of problem:

    In the section of smb.conf(5) that describes the "default case"
    parameter, the structure of the sentences and lack of punctuation
    leaves them open to a number of interpretations.

Version-Release number of selected component (if applicable):

    samba-3.0.28-0.el5.8
    samba-3.0.33-3.7.el5

How reproducible:

    Every time.

Steps to Reproduce:

    1. man smb.conf
    2. search for "default case"
    3. Read the paragraphs that follow
  
Actual results:

    Confusing description of the "default case" parameter.

Expected results:

    A clear description of the parameter which yields only one understanding.

Additional info:

    Suggested wording for this paragraph is as follows:

       default case = upper/lower
           controls what the default case is for new filenames
           (ie. files that don“t currently exist in the
           filesystem). Default _lower_. IMPORTANT NOTE: As part of
           the optimizations for directories containing large numbers
           of files, the following special case applies.  If the
           options _case_sensitive_=_yes_, _preserve_case_=_No_, and
           _short_preserve_case_=_No_ are set, then the case of _all_
           incoming client filenames, not just new filenames, will be
           modified.  See additional notes below.

Comment 5 errata-xmlrpc 2011-05-19 13:14:26 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0582.html