And then there's all of the extra sourcing of profiles from stuff like /etc/profile.d, /etc/profile.local, .bash_profile, .profile, .bashrc, and probably a heap of other places that I'm sure I don't know about.
But, yes, we were satisfied with the default profile chain that has worked the same for at least SLES9 and SLES10. But, this recent version of aaa_base has changed it...well, at least for us it has. The Novell tech hasn't been able to reproduce the problem as yet. I know what the problem is and can easily fix it, but I don't want to have to worry about it everytime I upgrade aaa_base. I could probably throw a workaround in /etc/profile.d I suppose... Leland On Mon, Aug 23, 2010 at 12:13 PM, Richard Troth <vmcow...@gmail.com> wrote: > You saying that you had no issues until you upgraded that package? > > I cannot address that package specifically, but I can share tears and > whine with you over the lack of cluefulness about how profiling is > handled. It not just Linux, but it's worse in Linux than other > Unix/POSIX. When Project Athena gave us X Windows, there was some > provision to get it right, but that was lost on the distributors (and > evidently on both the GNome developers and the KDE developers), so the > problem is even worse in a GUI environment than pure shell. > > I guess the summary report would be: I have had so many problems with > the distributed profiling that I always discard the .bashrc and > .bash_profile mandated from /etc/skel and install my own .profile > (usually withOUT shell rc). If they follow the rules, every Bourne > compatible shell will source that when you "log in". (Definition of > "log in" may still vary, and sadly DOES NOT include logging in to most > graphical desktops.) With care (and I don't mean much) you can have > C-Shell variants also source $HOME/.profile and safely return to their > expected behavior. > > I usually set my default shell to /bin/sh in case the environment goes > multi-platform, but that still does not fix the profiling problems. > > -- R; <>< > > > > > > On Mon, Aug 23, 2010 at 10:40, Leland Lucius <lluc...@homerow.net> wrote: > > Specifically, has your default PS1 prompt behavior changed? How about > > the sourcing of your private .bashrc? Do you have your default shell > > set to /bin/sh? > > > > Just curious if anyone else is having issues. > > > > Thanks, > > > > Leland > > > > ---------------------------------------------------------------------- > > For LINUX-390 subscribe / signoff / archive access instructions, > > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > > visit > > http://www.marist.edu/htbin/wlvindex?LINUX-390 > > ---------------------------------------------------------------------- > > For more information on Linux on System z, visit > > http://wiki.linuxvm.org/ > > > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
