[英]After installing CUDA on Tegra Tx1 and sourcing the bashrc it will not find NVCC
[英]Shell often exits after sourcing .bashrc file. Caused by infinite loop in Nvm
我編輯了原始帖子以消除紅鯡魚並更新最新的.bashrc
。
我有一個本地 Mac(使用 Zsh)和 ssh 到基於 EC2 的 linux 開發箱(使用 Bash)。
當我在我的 linux 計算機上獲取source ~/.bashrc
時,我的 shell經常退出。 我說“經常”是因為它不一致。 我只是嘗試兩次運行相同的命令,但問題只出現了第二次。 如果我在 tmux session 中進行采購,也會發生此問題,因此這不是 ssh 問題。 當我添加PS4=':${BASH_SOURCE[0]##*/}:$LINENO+'; set -x
在.bashrc
文件的頂部PS4=':${BASH_SOURCE[0]##*/}:$LINENO+'; set -x
,我只看到一條 stream 的::.bashrc:126+cdnvm /home/jalvarado
消息。 基於這個 output,我認為最后一個成功執行的命令是alias cd='cdnvm'
。
::.bashrc:124+'[' -s /home/jalvarado/.nvm/bash_completion ']'
::.bashrc:124+. /home/jalvarado/.nvm/bash_completion
:::bash_completion:5+command -v nvm
:::bash_completion:86+[[ -n '' ]]
:::bash_completion:96+complete -o default -F __nvm nvm
::.bashrc:167+alias cd=cdnvm
::.bashrc:168+cdnvm /home/jalvarado
::.bashrc:126+cdnvm /home/jalvarado
::.bashrc:126+cdnvm /home/jalvarado
::.bashrc:126+cdnvm /home/jalvarado
::.bashrc:126+cdnvm /home/jalvarado
...
::.bashrc:126+cdnvm /home/jalvarado
::.bashrc:126+cdnvm /home/jalvarado
::.bashrc:126+cdnvm /home/jalvarado
::.bashrc:126+cdnvm /home/jalvarado
Connection to devrestricted-jalvarado.ec2.pin220.com closed.
盡管如此,我開始一個新的 shell 沒有問題。 當我將 ssh 放入我的 devbox 或啟動新的 tmux session 時,我看不到任何 output。 事實上,我不再在 .bashrc 中看到“hello”作為我的echo "hello"
命令的一部分,我之前用它來調試,直到 echo 神秘地消失了。
我不知道如何調查這個。 有人有建議嗎?
這是我的.bashrc
文件的全部內容。 幾乎所有這些都是以編程方式生成的(不是由我生成的)。 我手動添加的唯一行是底部的 pyenv 行和最頂部的調試行。
# For debugging
PS4=':${BASH_SOURCE[0]##*/}:$LINENO+'; set -x
# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples
# If not running interactively, don't do anything
case $- in
*i*) ;;
*) return;;
esac
# don't put duplicate lines or lines starting with space in the history.
# See bash(1) for more options
HISTCONTROL=ignoreboth
# append to the history file, don't overwrite it
shopt -s histappend
# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
HISTSIZE=1000
HISTFILESIZE=2000
# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS.
shopt -s checkwinsize
# If set, the pattern "**" used in a pathname expansion context will
# match all files and zero or more directories and subdirectories.
#shopt -s globstar
# make less more friendly for non-text input files, see lesspipe(1)
[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"
# set variable identifying the chroot you work in (used in the prompt below)
if [ -z "${debian_chroot:-}" ] && [ -r /etc/debian_chroot ]; then
debian_chroot=$(cat /etc/debian_chroot)
fi
# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
xterm-color|*-256color) color_prompt=yes;;
esac
# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt
#force_color_prompt=yes
if [ -n "$force_color_prompt" ]; then
if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
# We have color support; assume it's compliant with Ecma-48
# (ISO/IEC-6429). (Lack of such support is extremely rare, and such
# a case would tend to support setf rather than setaf.)
color_prompt=yes
else
color_prompt=
fi
fi
if [ "$color_prompt" = yes ]; then
PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
else
PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
fi
unset color_prompt force_color_prompt
# If this is an xterm set the title to user@host:dir
case "$TERM" in
xterm*|rxvt*)
PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1"
;;
*)
;;
esac
# enable color support of ls and also add handy aliases
if [ -x /usr/bin/dircolors ]; then
test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
alias ls='ls --color=auto'
#alias dir='dir --color=auto'
#alias vdir='vdir --color=auto'
alias grep='grep --color=auto'
alias fgrep='fgrep --color=auto'
alias egrep='egrep --color=auto'
fi
# colored GCC warnings and errors
#export GCC_COLORS='error=01;31:warning=01;35:note=01;36:caret=01;32:locus=01:quote=01'
# some more ls aliases
alias ll='ls -alF'
alias la='ls -A'
alias l='ls -CF'
# Add an "alert" alias for long running commands. Use like so:
# sleep 10; alert
alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]\s*alert$//'\'')"'
# Alias definitions.
# You may want to put all your additions into a separate file like
# ~/.bash_aliases, instead of adding them here directly.
# See /usr/share/doc/bash-doc/examples in the bash-doc package.
if [ -f ~/.bash_aliases ]; then
. ~/.bash_aliases
fi
# enable programmable completion features (you don't need to enable
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile
# sources /etc/bash.bashrc).
if ! shopt -oq posix; then
if [ -f /usr/share/bash-completion/bash_completion ]; then
. /usr/share/bash-completion/bash_completion
elif [ -f /etc/bash_completion ]; then
. /etc/bash_completion
fi
fi
export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh" # This loads nvm
[ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion" # This loads nvm bash_completion
cdnvm() {
cd "$@";
nvm_path=$(nvm_find_up .nvmrc | tr -d '\n')
# If there are no .nvmrc file, use the default nvm version
if [[ ! $nvm_path = *[^[:space:]]* ]]; then
declare default_version;
default_version=$(nvm version default);
# If there is no default version, set it to `node`
# This will use the latest version on your machine
if [[ $default_version == "N/A" ]]; then
nvm alias default node;
default_version=$(nvm version default);
fi
# If the current version is not the default version, set it to use the default version
if [[ $(nvm current) != "$default_version" ]]; then
nvm use default;
fi
elif [[ -s $nvm_path/.nvmrc && -r $nvm_path/.nvmrc ]]; then
declare nvm_version
nvm_version=$(<"$nvm_path"/.nvmrc)
declare locally_resolved_nvm_version
# `nvm ls` will check all locally-available versions
# If there are multiple matching versions, take the latest one
# Remove the `->` and `*` characters and spaces
# `locally_resolved_nvm_version` will be `N/A` if no local versions are found
locally_resolved_nvm_version=$(nvm ls --no-colors "$nvm_version" | tail -1 | tr -d '\->*' | tr -d '[:space:]')
# If it is not already installed, install it
# `nvm install` will implicitly use the newly-installed version
if [[ "$locally_resolved_nvm_version" == "N/A" ]]; then
nvm install "$nvm_version";
elif [[ $(nvm current) != "$locally_resolved_nvm_version" ]]; then
nvm use "$nvm_version";
fi
fi
}
alias cd='cdnvm'
cd $PWD
export PYENV_ROOT="$HOME/.pyenv"
command -v pyenv >/dev/null || export PATH="$PYENV_ROOT/bin:$PATH"
eval "$(pyenv init -)"
echo "hello"
xtrace 日志顯示的問題是 cdnvm 中的cd
由於alias cd=cdnvm
cdnvm
調用cdnvm
。
要修復它,請更改:
cdnvm() {
cd "$@"
至
cdnvm() {
builtin cd "$@";
...強制使用cd
的原始/內置副本,繞過別名。
事實證明,我的 linux 機器的 nvm 代碼已過時。 NVM 去年修復了一個無限循環問題。 我建議使用他們擁有的最新版本的代碼。
他們的解決方案類似於@Charles 的解決方案:使用command cd
而不是僅使用cd
,他們給它起了別名,從而創建了一個無限循環。
聲明:本站的技術帖子網頁,遵循CC BY-SA 4.0協議,如果您需要轉載,請注明本站網址或者原文地址。任何問題請咨詢:yoyou2525@163.com.