https://bugzilla.novell.com/show_bug.cgi?id=244788 ------- Comment #19 from suse@tlinx.org 2007-03-13 20:55 MST ------- Tobias, please note -- the comments in /etc/skel/.bashrc are not necessarily portable from release to release nor to other environments. Those comments are not part of the standard "bash" distribution. I've used bash on Irix, Redhat, Mandrake, Windows with Microsoft's POSIX compatible subsystem and with Cygwin. You can rely on .bashrc being called from /etc/profile for now, but it is not standard usage. For myself, I already do something similar, but have my /etc/profile.local and my local ~/.bashrc both call common initialization files. This works in a heterogeneous environment. The problem recently has to do with /etc/bash.bashrc calling /etc/profile which has ended up calling the users ~/.bashrc twice. I got bitten by this change in non-interactive "ssh" sessions (i.e. it shouldn't have affected interactive, login sessions). But because my local .bashrc was called twice I got errors on non-interactive ssh. Example: ishtar:law> ssh astara echo hi /etc/local/vars.sh: line 46: typeset: _prg_tty: readonly variable /etc/local/vars.sh: line 49: typeset: _prg_id: readonly variable /etc/local/vars.sh: line 54: _sh_interactive_shell: readonly variable /etc/local/vars.sh: line 72: typeset: USER: readonly variable /etc/local/vars.sh: line 77: typeset: _sh_LOGNAME_: readonly variable /etc/local/vars.sh: line 78: typeset: LOGNAME: readonly variable /etc/local/vars.sh: line 81: unset: HOME: cannot unset: readonly variable /etc/local/vars.sh: line 82: typeset: HOME: readonly variable /etc/local/vars.sh: line 201: typeset: _vars_read_: readonly variable /etc/local/vars.sh: line 203: typeset: PERL5LIB: readonly variable hi My suggestion on modifying "~/.profile" was concerning _new_ users -- not existing ones, so it wouldn't modify existing .profile settings and users would continue to get behavior they were already used to. -- 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, or are watching someone who is.