On Fri, 2006-06-16 at 10:00 +0200, Marius Roets wrote:
Any ideas why this happens. (cut discussion of multiple PATH insertions/runs) I am using Suse 10.0 btw.
It means that the .bashrc is getting run several times, pre-pending the new path to it. Or it could be that the pre-pend has been added in another file that you didn't know about. An easy way to check is to remove the pre-pend from your .bashrc, logout and then log back in to see. I know Red Hat and SuSE different logic for profile, .bashrc, .bash_profile, etc... between user, system, etc... I haven't gotten the entire logic flow down for SuSE, and I'd be very interested if there is a document, FAQ, HOWTO, etc... out there that shows the _entire_logic_ of what and how different system and user files are executed in what order for a bash login shell under SuSE. One thing Red Hat does in its system-wide /etc/bashrc is offer a function called "pathmunge()" to avoid such a scenario, but I don't think that's LSB. I assume SuSE has something similar? Possibly more LSB-compliant? -- Bryan J. Smith Professional, technical annoyance mailto:b.j.smith@ieee.org http://thebs413.blogspot.com ---------------------------------------------------------- The existence of Linux has far more to do with the breakup of AT&T's monopoly than anything Microsoft has ever done. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com