https://bugzilla.novell.com/show_bug.cgi?id=244788 suse@tlinx.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|suse@tlinx.org | ------- Comment #4 from suse@tlinx.org 2007-02-17 17:22 MST ------- The behavior of bash conforms to the standard, listed behavior of "bash" ( :-) ). Saying it is "broken" is a matter of being able to read the manpage or not. I had problems at some point in the past with wanting variables initialized no matter what the session. I read the manpage rather than filing a bug against SuSE's bash and adopted my scripts to work with the documented behavior. Note at this point -- it's not that I cannot figure out a way _around_ SuSE's non-standard behavior. I to have variables in my init files to detect when I've already called my scripts or not. It's that SuSE is breaking documented compatibility. I understand the need to have a common setup for variables. I chose to do this with an explicitly named "common.sh" called by both. The problem created by the SuSE solution is that in addition to setting up session variables, it is also calling the user's "/etc/profile.local" -- thus doing the users "per-login" initialization more than once. I also have a similar call to "profile" from my system's local "bashrc" -- I make sure the "per-login" variables are set in my /etc/bashrc.local and if not, I call my /etc/profile.local script. However, in my case -- my local "profile" script does things only intended to be called once/login. Variables and settings that need to be set for both "bashrc" and "profile" are in the "common" file and are only called once. Thus I solve my need for both per-login settings and having one place for common settings. Having bashrc call profile to set "common settings" has unwanted side effects of also calling any -per-login processing. I could see it being more of a problem if someone relied on "bash_logoff" to be called at end of any session started with "profile" (as is would be normal if profile was only called for login sessions). In a way, SuSE is "dumbing down" "bash" because people are too lazy or ignorant to do things "right" -- yeah, makes it easy for the typical "Microsoft" type user who is computer illiterate, but then it bites people who bothered to read the manual (almost never a "Good Thing"). Hopefully this points to a backwards compatible way to make everybody happy (other than anyone who has to implement and test the change :-)). -- 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.