From c2b0311331607cdbe97c3641061d7267dc2677c5 Mon Sep 17 00:00:00 2001 From: Ben Mares Date: Thu, 3 Feb 2022 19:11:33 +0100 Subject: [PATCH] Improve wording of comment --- base-notebook/start.sh | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/base-notebook/start.sh b/base-notebook/start.sh index eab3dc84..05c10376 100755 --- a/base-notebook/start.sh +++ b/base-notebook/start.sh @@ -190,10 +190,11 @@ if [ "$(id -u)" == 0 ] ; then # used `env_delete` from /etc/sudoers. It has higher priority than the # `--preserve-env` flag and the `env_keep` configuration. # - # - We preserve PATH and PYTHONPATH explicitly. Note however that PATH is - # irrelevant to how the above sudo command resolves the path of `${cmd[@]}`. - # Sudo uses the "secure_path" variable we modified above in - # /etc/sudoers.d/path. (PATH is useful e.g. when `${cmd[@]}` is `bash`.) + # - We preserve PATH and PYTHONPATH explicitly. Note however that sudo + # resolves `${cmd[@]}` using the "secure_path" variable we modified + # above in /etc/sudoers.d/path. Thus PATH is irrelevant to how the above + # sudo command resolves the path of `${cmd[@]}`. The PATH will be relevant + # for resolving paths of any subprocesses spawned by `${cmd[@]}`. # The container didn't start as the root user, so we will have to act as the # user we started as.