ログインの有無にかかわらずユーザーを切り替えるときの PATH 環境変数の動作

Question

ユーザーとしてログインしてから別のユーザーに切り替えると、PATHログインの有無にかかわらず切り替えが行われると環境変数が変更されます。次のスニペットを参照してください。

$ ssh -i ~/.ssh/ubuntu.pem [email protected]
ubuntu@kingdom:~$ echo $PATH | tr ':' '\n' | grep sbin
/usr/local/sbin
/usr/sbin
/sbin
ubuntu@kingdom:~$ sudo su -l foo # with login
foo@kingdom:~$ echo $PATH | tr ':' '\n' | grep sbin
foo@kingdom:~$ exit
logout
ubuntu@kingdom:~$ sudo su foo # without login
foo@kingdom:/home/ubuntu$ echo $PATH | tr ':' '\n' | grep sbin
/usr/local/sbin
/usr/sbin
/sbin
foo@kingdom:/home/ubuntu$ exit
exit

$ ssh -o -i ~/.ssh/foo.pem [email protected]
foo@kingdom:~$ echo $PATH | tr ':' '\n' | grep sbin
/usr/local/sbin
/usr/sbin
/sbin
foo@kingdom:~$ sudo su -l ubuntu
ubuntu@kingdom:~$ echo $PATH | tr ':' '\n' | grep sbin
ubuntu@kingdom:~$

ご覧のとおり、ubuntuユーザー を使用して Ubuntu ボックスにログインし、ユーザーを確認するとPATH、 が/sbin存在します。fooユーザーに切り替えて を確認すると、切り替え時に (ログイン用) が指定されPATHたかどうかに応じて影響を受けます-l。 ログインが行われると、 がPATH影響を受け、 は/sbin存在しません。 ユーザーが切り替えられたときにログインがスキップされると、これは発生しません。

fooユーザーとして Ubuntu ボックスに接続すると、 がPATH保持されます。ユーザー/sbinに切り替えてを確認すると、ログインでユーザーに切り替えた場合は は存在しません。ubuntuPATH/sbinubuntu

ちなみに私はbashを使っています。

ユーザーのbashとプロファイル設定の一部を削除してみましたが、効果はありませんでした。以下を参照してください。

ubuntu@kingdom:~$ echo $PATH | tr ':' '\n' | grep sbin
ubuntu@kingdom:~$ sudo rm /home/foo/.bash /home/foo/.bashrc /home/foo/.profile
ubuntu@kingdom:~$ sudo su -l foo
foo@kingdom:~$ echo $PATH | tr ':' '\n' | grep sbin
foo@kingdom:~$ exit
logout
ubuntu@kingdom:~$ sudo rm -rf /etc/profile.d/
ubuntu@kingdom:~$ sudo su -l foo
foo@kingdom:~$ echo $PATH | tr ':' '\n' | grep sbin
foo@kingdom:~$ exit
logout
ubuntu@kingdom:~$ cat /etc/environment
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games"

更新 (TL;DR):

ubuntu@kingdom:~$ echo $PATH | tr ':' '\n' | grep sbin
/usr/local/sbin
/usr/sbin
/sbin
ubuntu@kingdom:~$ sudo su ubuntu
ubuntu@kingdom:~$ echo $PATH | tr ':' '\n' | grep sbin
/usr/local/sbin
/usr/sbin
/sbin
ubuntu@kingdom:~$ exit
exit
ubuntu@kingdom:~$ sudo su -l ubuntu
ubuntu@kingdom:~$ echo $PATH | tr ':' '\n' | grep sbin
ubuntu@kingdom:~$ exit
logout

更新2:

コメントで、PATH値を印刷するように言及している人がいました。そのため、読み取りチェーン内の各ファイルについて、各ファイルの最初と最後の行に印刷を追加しましたPATH。これでさらに混乱しました。以下のスニペットを参照してください。

$ ssh -i ~/.ssh/ubuntu.pem [email protected]
/etc/profile: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
/etc/bash.bashrc: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
/etc/bash.bashrc: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
/etc/profile: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
/home/ubuntu/.profile: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
/home/ubuntu/.bashrc: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
/home/ubuntu/.bashrc: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
/home/ubuntu/.profile: /home/ubuntu/bin:/home/ubuntu/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin

ubuntu@kingdom:~$ sudo su -l ubuntu
/etc/profile: /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
/etc/bash.bashrc: /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
/etc/bash.bashrc: /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
/etc/profile: /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/snap/bin
/home/ubuntu/.profile: /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/snap/bin
/home/ubuntu/.bashrc: /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/snap/bin
/home/ubuntu/.bashrc: /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/snap/bin
/home/ubuntu/.profile: /home/ubuntu/bin:/home/ubuntu/.local/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/snap/bin
ubuntu@kingdom:~$ exit
logout

ubuntu@kingdom:~$ sudo su ubuntu
/etc/bash.bashrc: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
/etc/bash.bashrc: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
/home/ubuntu/.bashrc: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
/home/ubuntu/.bashrc: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games

1. なぜそのように動作するのでしょうか?
2. どうすればデバッグして、ログインしたユーザーに切り替えたときに がPATH保持されることを確認できますか?/sbin

Answer 1

どの設定ファイルを読み取るかを決定するオプションman bashを 確認してください:-l

INVOCATION
   A login shell is one whose first character of argument zero is a -, or one started with the --login option.

   An interactive shell is one started without non-option arguments and without the -c option whose standard input and error are both connected to  ter‐
   minals (as determined by isatty(3)), or one started with the -i option.  PS1 is set and $- includes i if bash is interactive, allowing a shell script
   or a startup file to test this state.

   The following paragraphs describe how bash executes its startup files.  If any of the files exist but cannot be read, bash reports an error.   Tildes
   are expanded in filenames as described below under Tilde Expansion in the EXPANSION section.

   When  bash is invoked as an interactive login shell, or as a non-interactive shell with the --login option, it first reads and executes commands from
   the file /etc/profile, if that file exists.  After reading that file, it looks for ~/.bash_profile, ~/.bash_login, and ~/.profile, in that order, and
   reads  and executes commands from the first one that exists and is readable.  The --noprofile option may be used when the shell is started to inhibit
   this behavior.

   When a login shell exits, bash reads and executes commands from the file ~/.bash_logout, if it exists.

   When an interactive shell that is not a login shell is started, bash reads and executes commands from /etc/bash.bashrc and ~/.bashrc, if these  files
   exist.  This may be inhibited by using the --norc option.  The --rcfile file option will force bash to read and execute commands from file instead of
   /etc/bash.bashrc and ~/.bashrc.

   When bash is started non-interactively, to run a shell script, for example, it looks for the variable BASH_ENV in the environment, expands its  value
   if it appears there, and uses the expanded value as the name of a file to read and execute.  Bash behaves as if the following command were executed:
          if [ -n "$BASH_ENV" ]; then . "$BASH_ENV"; fi
   but the value of the PATH variable is not used to search for the filename.

   If  bash is invoked with the name sh, it tries to mimic the startup behavior of historical versions of sh as closely as possible, while conforming to
   the POSIX standard as well.  When invoked as an interactive login shell, or a non-interactive shell with the --login option,  it  first  attempts  to
   read  and  execute  commands  from  /etc/profile  and  ~/.profile, in that order.  The --noprofile option may be used to inhibit this behavior.  When
   invoked as an interactive shell with the name sh, bash looks for the variable ENV, expands its value if it is defined, and uses the expanded value as
   the  name of a file to read and execute.  Since a shell invoked as sh does not attempt to read and execute commands from any other startup files, the
   --rcfile option has no effect.  A non-interactive shell invoked with the name sh does not attempt to read any other startup files.  When  invoked  as
   sh, bash enters posix mode after the startup files are read.

   When bash is started in posix mode, as with the --posix command line option, it follows the POSIX standard for startup files.  In this mode, interac‐
   tive shells expand the ENV variable and commands are read and executed from the file whose name is the expanded value.  No other  startup  files  are
   read.

   Bash  attempts to determine when it is being run with its standard input connected to a network connection, as when executed by the remote shell dae‐
   mon, usually rshd, or the secure shell daemon sshd.  If bash determines it is being run  in  this  fashion,  it  reads  and  executes  commands  from
   ~/.bashrc and ~/.bashrc, if these files exist and are readable.  It will not do this if invoked as sh.  The --norc option may be used to inhibit this
   behavior, and the --rcfile option may be used to force another file to be read, but neither rshd nor sshd  generally  invoke  the  shell  with  those
   options or allow them to be specified.

   If the shell is started with the effective user (group) id not equal to the real user (group) id, and the -p option is not supplied, no startup files
   are read, shell functions are not inherited from the environment, the SHELLOPTS, BASHOPTS, CDPATH, and GLOBIGNORE variables, if they  appear  in  the
   environment,  are ignored, and the effective user id is set to the real user id.  If the -p option is supplied at invocation, the startup behavior is
   the same, but the effective user id is not reset.

あなたの質問に答える 2 つの段落は次のとおりです。

bash が対話型ログイン シェルとして、または --login オプション付きの非対話型シェルとして呼び出されると、最初に /etc/profile ファイルが存在する場合はそこからコマンドを読み取って実行します。そのファイルを読み取った後、~/.bash_profile、~/.bash_login、~/.profile をこの順序で検索し、最初に存在し読み取り可能なファイルからコマンドを読み取って実行します。シェルの起動時に --noprofile オプションを使用すると、この動作を禁止できます。

ログイン シェルではない対話型シェルが起動されると、bash は /etc/bash.bashrc および ~/.bashrc ファイルが存在する場合、そこからコマンドを読み取って実行します。これは、--norc オプションを使用して抑制できます。--rcfile ファイル オプションは、bash に /etc/bash.bashrc および ~/.bashrc ではなくファイルからコマンドを読み取って実行するように強制します。