Re: Shell startup (was: how to troubleshoot PASE errors?)

On Fri, Oct 5, 2018 at 2:06 PM Jack Woehr
<jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:

And set your user shells in PASE to /QOpenSys/pkgs/bin/bash

That sounds like perfectly reasonable advice.

But it looks to me (and keep in mind I have not been much of a Unix
shell user in more than 20 years) that your .profile is more
complicated than it has to be:

# Optional test if needed to detect if we're in a PASE shell
# /QSYS.LIB/QSHELL.LIB/UNAME.PGM > /dev/null 2>&1
# if [ $? != 0 -a "$SHELL" != "/QOpenSys/pkgs/bin/bash" ]
# then
# exec /QOpenSys/pkgs/bin/bash
# fi
if [ -n "$BASH_VERSION" ]; then
# include .bashrc if it exists
if [ -f "$HOME/.bashrc" ]; then
. "$HOME/.bashrc"
fi
fi

If we're currently *in* bash, then .bashrc should have already been
run automatically, if it exists. Why do you explicitly include it?

My own .profile just consists of a single line to exec bash. (And then
some actual settings in .bashrc.)

John Y.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD