Bug 858432
Summary: | Avoid logs related to printers from samba | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Scott Haines <shaines> |
Component: | glusterd | Assignee: | Jose A. Rivera <jarrpa> |
Status: | CLOSED ERRATA | QA Contact: | Sudhir D <sdharane> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2.1 | CC: | amarts, crh, gluster-bugs, kparthas, rhs-bugs, sdharane, spalai, vagarwal, vbellur |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | 844188 | Environment: | |
Last Closed: | 2013-09-23 22:39:13 UTC | Type: | Bug |
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: | 844188 | ||
Bug Blocks: |
Comment 2
Ujjwala
2013-08-01 07:42:46 UTC
Jose , Small change. 1st# "show add printers wizard" should be --->"show add printer wizard"(remove the 's' from the printers) 2nd# What I observed is we can't comment at the end of parameters e.g kernel oplocks = no #Improves large file sequential We should comment from the beginning of the line. In this case just before the parameter we should give the comments like : #Improves large file sequential kernel oplocks = no Some quick research shows that the formatting I provided in BZ 844188 is incorrect. Samba does not allow trailing comments in the smb.conf file. The comment characters (';' and '#') must be the first (non-whitespace) thing on the line, otherwise the comment is seen as being part of the parameter value. This is because both ';' and '#' are legal within such values. Moving the comments to their own separate lines should solve the problem encountered by QE. Verified on Samba-glusterfs-3.6.9-156.2 build. Looks fine. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1262.html Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1262.html |