Mailinglist Archive: opensuse-bugs (4675 mails)

< Previous Next >
[Bug 642080] New: Cumulative changes to PATH under login csh/tcsh don't work when krb5-devel is installed
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Mon, 27 Sep 2010 15:57:50 +0000
  • Message-id: <bug-642080-21960@xxxxxxxxxxxxxxxxxxxxxxxx/>

Summary: Cumulative changes to PATH under login csh/tcsh don't
work when krb5-devel is installed
Classification: openSUSE
Product: openSUSE 11.3
Version: Final
Platform: Other
OS/Version: openSUSE 11.3
Status: NEW
Severity: Major
Priority: P5 - None
Component: Network
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: pkeller@xxxxxxxxxxxxxxxxx
QAContact: qa@xxxxxxx
Found By: ---
Blocker: ---

User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:
Gecko/20100914 SUSE/3.6.10-0.3.1 Firefox/3.6.10

/etc/profile.d/krb5.csh contains broken C-shell code that prevents cumulative
changes to the PATH environment variable being performed with the following
standard construction:

setenv PATH /path/to/new/bin:$PATH

The offending lines are:

set PATH="${PATH}:/usr/lib/mit/bin"
set PATH="${PATH}:/usr/lib/mit/sbin"

which create a new shell variable PATH that masks the environment variable PATH
in $ expansion. Probably what was intended are the following lines:

setenv PATH "${PATH}:/usr/lib/mit/bin"
setenv PATH "${PATH}:/usr/lib/mit/sbin"

Reproducible: Always

Steps to Reproduce:
1. Start with an openSUSE 11.3 system that has krb5-devel installed.
2. ssh into this system as a user that has /bin/tcsh as their login shell (or
otherwise source /etc/csh.login from a C-shell when CSHRCREAD is unset)
3. Create two new directories for testing:

mkdir $HOME/bina $HOME/binb

4. Create an executable script in the first directory:

cat > $HOME/bina/
echo hello
chmod a+x $HOME/bina/

5. Add the first directory to PATH using this construction:

setenv PATH $HOME/bina:$PATH

6. Verify that the script works:

7. Add second directory to PATH:

setenv PATH $HOME/binb:$PATH

8. Verify that script no longer runs:

Actual Results:
Step 6 above produces the result:


Step 8 produces: Command not found.

Expected Results:
Step 8 should produce the same result as step 6

Most scripts that use the 'setenv PATH ...' construction rather than the 'set
path=(...)' one will be rendered ineffective by this bug.

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >
Follow Ups