Red Hat Bugzilla – Bug 123621
/etc/profile unsets "pathmunge" too early
Last modified: 2015-03-04 20:13:55 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040116
Description of problem:
In /etc/profile, after a few "pathmunge" statements, that function is
However, this prevents users and RPM package makers to use the
function in files that get installed in /etc/profile.d
Case in point, i want to set a PATH component for my Java
installation. Since editing /etc/pofile is not nice, and since making
that kind of changes is best accomplished with a new file in
/etc/profile, i'd like to be able to use the pathmunge() function in
my custom file in /etc/profile.d
However, i cannot accomplish that unless i comment out "unset pathmunge".
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.add a file to /etc/profile.d that uses the pathmunge() function
Actual Results: the pathmunge() call fails
Expected Results: pathmunge() should work in files in /etc/profile.d
Will be in 2.5.34-1, thanks!
Unfortunately recent versions (at least as of FC4 and FC5test1) of the setup
package also pull in the profile.d snippets directly from /etc/bashrc where
pathmunge is not defined, so it cannot be used anyway :(
OK, i've looked at it a little more closely.
Problem is that for non login shells bashrc now sources the profile.d files. The
next rawhide version will contain a fix that includes pathmunge in bashrc again
for that case.
Read ya, Phil