Bug 1318656 - document supported ENV variables in man pages
Summary: document supported ENV variables in man pages
Keywords:
Status: CLOSED DUPLICATE of bug 1378742
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pcs
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: Tomas Jelinek
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-17 13:06 UTC by Radek Steiger
Modified: 2016-10-26 13:16 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-26 13:16:10 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1315627 0 high CLOSED [RFE] pcsd should handle http proxy environment variables better 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1347335 0 medium CLOSED built-in documentation fixes 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1352047 0 medium CLOSED [cli] possibly dangerous treatment of environment variables when running a subprocess 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1378742 0 medium CLOSED create manpage for pcsd 2021-02-22 00:41:40 UTC

Internal Links: 1315627 1347335 1352047 1378742

Description Radek Steiger 2016-03-17 13:06:57 UTC 
PCS daemon supports reading several various environmental variables that are usually set via initscript or systemd through /etc/sysconfig/pcsd, but are not documented anywhere at this point.

So far we expose following ones in /etc/sysconfig/pcsd and should mention them in man pages:

PCSD_DEBUG
RACK_ENV
DISABLE_GUI

Ideally, we should provide a general description of the supported ENV variables without being tied to /etc/sysconfig, because a user might want to set these in other ways (and also other distributions might use different approach than what we do in RHEL).

We might consider other ENV variables that pcsd already understands, but most of them are for internal use only.
Comment 1 Jan Pokorný [poki] 2016-04-18 07:59:05 UTC 
To articulate that aloud, also the environment variables the underlying
components are known to honor should be mentioned.

See, for instance, https_proxy and no_proxy, just as these get documented
in WGET(1) ... related [bug 1315627].
Comment 2 Tomas Jelinek 2016-10-26 13:16:10 UTC 
pcsd environment variables are covered by bz1378742
pcs environment variables are covered by bz1352047

*** This bug has been marked as a duplicate of bug 1378742 ***
Note You need to log in before you can comment on or make changes to this bug.