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 1099275

Summary: mailx documentation has conflicting information about environment vairables and config files
Product: Red Hat Enterprise Linux 6 Reporter: GE Scott Knauss <sknauss>
Component: man-pages-overridesAssignee: Jan Chaloupka <jchaloup>
Status: CLOSED ERRATA QA Contact: Iveta Wiedermann <isenfeld>
Severity: low Docs Contact:
Priority: medium    
Version: 6.5CC: isenfeld, jchaloup, klamb, ovasik, pschiffe, thgardne
Target Milestone: rcKeywords: ManPageChange, Patch
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: man-pages-overrides-6.6.2-1.el6 Doc Type: Bug Fix
Doc Text:
Cause: incomplete information about unsetting of environment variables were presented Consequence: information of possible unsetting of environment variables were missing Fix: information about unsetting of environment variables provided Result: man page is updated
Story Points: ---
Clone Of:
: 1109294 (view as bug list) Environment:
Last Closed: 2014-10-14 07:27:11 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:    
Bug Blocks: 1109294, 1119276    
Attachments:
Description Flags
mailx.1: environment variables conflict
pschiffe: review+
mailx-12.4-man-variable.patch
none
mailx-12.4-man-variable.patch none

Description GE Scott Knauss 2014-05-20 01:54:45 UTC
Description of problem:

The man page contains the following:

"
NOTES

       Variables in the environment passed to mailx cannot be unset.
"

<snip>
"
   Variable options
       Options are controlled via set and unset commands,  see  their  entries
       for  a  syntax  description.   An option is also set if it is passed to
       mailx as part of the environment (this is not  restricted  to  specific
       variables  as  in the POSIX standard).  A value given in a startup file
       overrides a value imported from the environment.  Options may be either
       binary,  in  which  case it is only significant to see whether they are
       set or not; or string, in which case the actual value is of interest.

"

The first appears to be the current state of the code.


Version-Release number of selected component (if applicable):
12.4-7.el6.x86_64

How reproducible:

man mailx


Steps to Reproduce:

1. mail mailx 

Actual results:

See Description

Expected results:

The sentence "A value given in a startup file overrides a value imported from the environment." should be removed from the man page.


Additional info:

This issue was found when the user upgraded from RHEL 5 to RHEL 6 and a script failed due to the debug variable being defined as a function in a script that also called mailx. This caused mailx to go in to debug mode and not send email.

Comment 2 Jan Chaloupka 2014-06-06 08:48:17 UTC
Does it make sence for ou, Peter, to remove the sentence "A value given in a startup file overrides a value imported from the environment."?

Comment 3 Peter Schiffer 2014-06-06 10:32:55 UTC
Yes, it looks reasonable. Thanks.

Comment 4 Jan Chaloupka 2014-06-06 12:39:46 UTC
Created attachment 902912 [details]
mailx.1: environment variables conflict

Removing the sentence.

Comment 5 Thomas Gardner 2014-06-06 17:10:21 UTC
(In reply to Jan Chaloupka from comment #2)
> Does it make sence for ou, Peter, to remove the sentence "A value given in a
> startup file overrides a value imported from the environment."?

This does NOT sound reasonable to me.  I believe that sentence is still true.  I believe value GIVEN in a startup file does override a value imported from the environment.  The only thing is that a value from the environment can't be unset from the config file, only overriden with a new value.  I think the sentence needs to be there or the user will have no idea.  I would just repeat the caveat given at the end of the man page here, that's all.

Please, don't remove that sentence unless someone has found that it's not true.

Comment 6 Peter Schiffer 2014-06-09 12:53:40 UTC
Created attachment 904655 [details]
mailx-12.4-man-variable.patch

Ah, right. Override doesn't mean only unset. Thanks Thomas. I've updated the patch.

Comment 8 Peter Schiffer 2014-06-09 16:23:57 UTC
Created attachment 904792 [details]
mailx-12.4-man-variable.patch

fixed grammar

Comment 23 errata-xmlrpc 2014-10-14 07:27:11 UTC
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-2014-1382.html