On Fri, Mar 22, 2013 at 5:23 PM, R P Herrold <[email protected]> wrote: ... > > I am thinking that the > /etc/profile > method is your best bet if it is re-sourcing the log-in > environment or something wierd in the application's > 'installer'
Also hoping that the installer does not set ignorant values for PATH, CLASSPATH, or the JAVA_* variables. This brings to mind the continued degradation of profiling in Unix, especially in Linux. Originally, everyone signed in and got a shell prompt. There was /etc/profile (sourced first) and then $HOME/.profile (sourced second, so users got the last word w/r/t their environment). Then came X windows. Those developers did a great job, and you *can* get consistent profiling under the X/GUI login. But the concept has been lost, and most stock graphical signons fail. (GUI session startup often *does not* source either /etc/profile or $HOME/.profile, last I had time to check into it.) The only solution at present is sysadmin diligence, which is human intensive. It used to be easy enough to fix the session profiling, but as Linux has danced around from XFree86 to X.org, things have changed. Summary: If you're a sysadmin ... * You should ensure that /etc/profile is sourced for *all* signons, GUI or linemode. * You might also want for /usr/local/etc/profile (or some equivalent) to be sourced at signon. * You should ensure for $HOME/.profile is sourced at signon. -- -- R; <>< ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] 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/
