https://bugzilla.novell.com/show_bug.cgi?id=244788 suse@tlinx.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Comment #15 from suse@tlinx.org 2007-03-13 10:28 MST ------- Q: does "~/.bashrc still get called twice? The test for being within didn't encompass ~/.bashrc as it did "bash.bashrc". The calling of .bashrc twice upon a non-login ssh session is specifically what was causing my probs. ** Is it possible to attach the updated files to this bug for further testing? Tobias, question -- you want your local .bashrc called not only for non-logic shells, but also for login shells, yes? Is there something that would preclude you adding automating your sourcing of the file, upon login, by including it in the and of the login personalization files: ~/.bash_profile, ~/.bash_login, or ~/.profile? If you are only wanting "~/.bashrc" sourced for ssh logins, there is also "~/.ssh/rc". I wasn't clear why you hadn't automated sourcing ".bashrc" in your login script? If you are used to bash across multiple systems, .bashrc is only called at login if explicitly chosen (it's not the default). It maybe be called by the users .profile or from the system /etc/profile. Maybe that would work as a solution for here? If SuSE added a "~/.profile" to new users' home dirs that tested for and called .bashrc for users, that would provide a compatible way for user's to have their .bashrc called on login as well as non-login shells? -- 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.