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.
http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/6.1_Technical_Notes/bash.html
only relevant messages are now presented to user. (BZ#664468)
only relevant messages are now presented to users. (BZ#664468)
only relevant messages are now presented to the user. (BZ#664468)
http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/6.1_Technical_Notes/bind.html
The rndc.key is used by rndc utility
The rndc.key is used by rndc the utility
Users requiring the rndc utility should generate key themselves,
Users requiring the rndc utility should generate a key themselves,
Users requiring the rndc utility should generate the key themselves,
Consequently, "named" could not be stopped using the "/etc/init.d/named stop".
Consequently, "named" could not be stopped using "/etc/init.d/named stop".
Consequently, "named" could not be stopped using the "/etc/init.d/named stop" command.
named writes error message to the system log
named writes an error message to the system log
when bind-sdb package was installed.
when the bind-sdb package was installed.
when resolv.conf contained "search" keyword with no arguments host/nslookup/dig utilities failed to parse it correctly.
when resolv.conf contained the "search" keyword with no arguments, host/nslookup/dig utilities failed to parse it correctly.
The the dnssec-keygen
The dnssec-keygen
and allows to start named
and allows starting named
with this update, size, MD5 and the modification time of /etc/sysconfig/named configuration file is no longer checked
with this update: size, MD5 and the modification time of the /etc/sysconfig/named configuration file are no longer checked
http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/6.1_Technical_Notes/binutils.html
Missing bullets & punctuation:
fix strip to keep the address of an empty section consistent with its offset in the object (BZ#614443) if one of the input files is of a non-ELF format the linker may crash (BZ#680143) fix occasional crash in linker (BZ#697703)
Again:
add support for the large code model on PowerPC (BZ#663587) add support for ELF core dump notes sections for extra s390 registers (BZ#633448) add support for the new instructions in the System z196 processor (BZ#631540) add support for ELF objects with more then 65535 program headers (BZ#578661)
http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/6.1_Technical_Notes/cifs-utils.html
This was due to the --legacy-uid command line option for cifs.upcall not properly implementing.
This was due to the --legacy-uid command line option for cifs.upcall not being properly implemented.
Or not properly implementing *what*??
This patch ensures that it properly implements,
Incorrect usage of 'implements'.
This is unclear. Do you mean to say the mount is retried with a different (theoretically equivalent) value for one or more of those options? What if all 3 are used -- does it convert one or all? Does it retry with different combinations?
>mount.cifs did not handle numeric uid=, gid=, or cuid= options correctly, and would often return an error when they were specified. With this patch, a check is run to see if any error occurred by setting errno to 0 before the conversion. If one did then it will attempt to treat the value as a name, allowing them to be correctly handled. (BZ#696951)