![](https://seccdn.libravatar.org/avatar/a4139df10120ce151e457fd1faff018d.jpg?s=120&d=mm&r=g)
On 11/5/19 2:04 PM, David T-G wrote:
Robert, et al --
...and then Robert Munteanu said... % ... % So this is not about a new user vs existing ones, it's about how login % is achieved. I get the path that does not include $HOME/bin by: % % - logging in to tty1
This surprises me, since it is IS an actual login and will read your profile.
% - using xterm % - using gnome-terminal % - using tilix
These are likely not login shells but rather just shells, and so they won't read profile and do the fun stuff in there.
Well technically these are terminal emulators and not shells, shells are bash, zsh fish etc
% % So there's a clear difference how the paths are setup. Digging further, % I see some path work being done in /etc/profile: % % if test -z "$PROFILEREAD" ; then
Here's an interesting twist. If the variable indicating that you've already been through profile is empty then go ahead and do the next stuff, but don't repeat it.
% PATH=/usr/local/bin:/usr/bin:/bin % if test "$HOME" != "/" ; then % for dir in $HOME/bin/$CPU $HOME/bin ; do % test -d $dir && PATH=$dir:$PATH
It shouldn't be a factor in this case, since $PATH should be exported and inherited, but other things may not really happen when you think they would.
% done % fi % % (snip) % % But not sure why it does not work in my case.
Login vs just a shell.
% % Thanks, % Robert
HTH & HAND
:-D
-- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B