I am wondering what the best practice for a global .profile file would be,
and if used, would a personal .profile (/home/[user]/.profile) file be able
to override and/or add to the global settings.
The main reason I ask is I have a couple companies I'm doing nodeJS work
for. Jobs run to start SSHD and start up nodejs servers daily/after IPL and
they could run under any user id using QSH.
I remember years ago talking about using /QOpenSys/etc/profile but I
opened mine and had a note:
# /QOpenSys/etc/profile for IBM i
# DO NOT CHANGE /QOpenSys/etc/profile! It will be overwritten
# via PTF or system upgrade. Instead, add system-specific changes
# to /QOpenSys/etc/profile.local or add a file to
# /QOpenSys/etc/profile.d. Users can also add their own changes
# to ~/.profile (bsh, ksh, bash) ~/.login (csh), or ~/.bash_profile (bash)
I remember adding this a couple years ago when I was playing with things.
So now I'm wondering what would be the best practice... IBM seems to say
it's ok to edit this file. In fact, I'm sure I had this file like this
before V7R4 updgrade... so OS upgrade didn't seem to overwrite it.
Finally, are the profile files used in order global/personal or the other
way around? (I could test this, I thought I would ask).
Or am I barking up the wrong tree entirely? :)
Bradley V. Stone
MAILTOOL Benefit #15 <https://www.bvstools.com/mailtool.html
>: The ability
to add a Footer to each email sent using an IFS stream file.