https://bugzilla.novell.com/show_bug.cgi?id=827248
https://bugzilla.novell.com/show_bug.cgi?id=827248#c6
Dominique Leuenberger
The /etc/profile (for tcsh /etc/csh.login) will be read at login only, then the variable PROFILEREAD is set to avoid that parts of /etc/profile will be read for every shell started as login shell. Therefore in /etc/profile should only set the exported environment.
The variable PROFILEREAD, if not set, will also cause that in /etc/bash.bashrc the /etc/profile will be sourced, e.g. for an ssh session.
Thanks! That matches about what I found so far and is good to be 'documented' in this form. But it does not 'fix' the problem for VTE based terminals (yet) would you accept a patch into /etc/bash.bashrc which adds test -r /etc/profile.d/vte.sh -a ! -k /etc/profile.d/vte.sh && . /etc/profile.d/vte.sh ? This is in line with how profile.d treats it, with the sticky bit set it would be ignored (and as such can be 'overruled' by an admin). The general 'login' shell does not parse it, due to this part inside vte.sh: # Not running under vte? [ "${VTE_VERSION:-0}" -ge 3405 ] || return 0 as non-VTE terminals do not specify a VTE_VERSION -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.