2017-08-15 179 views
0

我在我的.bashrc文件中为Hcatalog添加了导出语句,最终导致了我的.basrc文件混乱。现在,即使我在我的cmd中打开了bashrc文件并删除了这两个导出语句,但我仍然无法运行任何命令。在ubuntu编辑bashrc文件后命令不工作

我目前的.bashrc文件:

>  # ~/.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 
>  [ -z "$PS1" ] && return 
> 
>  # 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) 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\]\[email protected]\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ 
> ' else 
>  PS1='${debian_chroot:+($debian_chroot)}\[email protected]\h:\w\$ ' fi unset color_prompt force_color_prompt 
> 
> # If this is an xterm set the title to [email protected]:dir case "$TERM" in xterm*|rxvt*) 
>  PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\[email protected]\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 
> 
> # 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 [ -f /etc/bash_completion ] && ! shopt -oq posix; then 
>  . /etc/bash_completion fi 
> 
> export JAVA_HOME=/usr/lib/jvm/java-6-openjdk-amd64 
> 
> export HADOOP_PREFIX=/home/itelligence/hadoop-1.2.0 export 
> PATH=$PATH:$HADOOP_PREFIX/bin 
> 
> export HADOOP_COMMON_HOME=/home/itelligence/hadoop-1.2.0 export 
> HADOOP_MAPRED_HOME=/home/itelligence/hadoop-1.2.0 export 
> HBASE_HOME=/home2/itelligence/hbase-0.94.20 export 
> HIVE_HOME=/home/itelligence/hive-0.12.0 
> 
> export PIG_PREFIX=/home/itelligence/pig-0.11.1 export 
> PATH=$PATH:$PIG_PREFIX/bin 
> 
> export HIVE_PREFIX=/home/itelligence/hive-0.12.0 export 
> PATH=$PATH:$HIVE_PREFIX/bin 
> 
> export HBASE_PREFIX=/home/itelligence/hbase-0.94.20 export 
> PATH=$PATH:$HBASE_PREFIX/bin 
> 
> export ZOOKEEPER_PREFIX=/home/itelligence/zookeeper-3.4.6 export 
> PATH=$PATH:$ZOOKEEPER_PREFIX/bin 
> 
> export SQOOP_PREFIX=/home/itelligence/sqoop-1.4.4.bin__hadoop-1.0.0 
> export PATH=$PATH:$SQOOP_PREFIX/bin export 
> FLUME_PREFIX=/home/itelligence/apache-flume-1.6.0-bin export 
> PATH=$PATH:$FLUME_PREFIX/bin 
> 
>  export CASSANDRA_PREFIX=/home/itelligence/apache-cassandra-2.0.8 
>  export PATH=$PAT4H:$CASSANDRA_PEFIX/bin 

而且对此我遇到的错误是: hadoop namenode -format hadoop:command not found

任何人都可以请帮我这。 TIA。

+0

我检查了我的.bashrc文件,已经为所需的出口声明我在接下来的llines .E。但我认识到一个错字,取而代之的是默认的basrc文件,它开始工作。感谢您的回应。 –

+0

最后一行使'PATH =:/ home/itelligence/apache-cassandra-2.0.0/bin',将您之前对PATH的所有修改都删除 - 提示:$ PAT4H的值是多少? – twalberg

回答

0

有很多错误。一半如果陈述,一些评论一些刚刚离开。而出口已经转移到了线的末端。

我想你应该重新设置文件:“#源/etc/bash.bashrc)” cp -f /etc/skel/.bashrc ~/

0

编辑您的.bashrc文件,删除后的所有内容并添加下面的行。

if [ -f /etc/bash_completion ] && ! shopt -oq posix; then 
    . /etc/bash_completion fi 

export JAVA_HOME=/usr/lib/jvm/java-6-openjdk-amd64 

export HADOOP_PREFIX=/home/itelligence/hadoop-1.2.0 
export PATH=$PATH:$HADOOP_PREFIX/bin 

export HADOOP_COMMON_HOME=/home/itelligence/hadoop-1.2.0 
export HADOOP_MAPRED_HOME=/home/itelligence/hadoop-1.2.0 
export HBASE_HOME=/home2/itelligence/hbase-0.94.20 
export HIVE_HOME=/home/itelligence/hive-0.12.0 

export PIG_PREFIX=/home/itelligence/pig-0.11.1 
export PATH=$PATH:$PIG_PREFIX/bin 

export HIVE_PREFIX=/home/itelligence/hive-0.12.0 
export PATH=$PATH:$HIVE_PREFIX/bin 

export HBASE_PREFIX=/home/itelligence/hbase-0.94.20 
export PATH=$PATH:$HBASE_PREFIX/bin 

export ZOOKEEPER_PREFIX=/home/itelligence/zookeeper-3.4.6 
export PATH=$PATH:$ZOOKEEPER_PREFIX/bin 

export SQOOP_PREFIX=/home/itelligence/sqoop-1.4.4.bin__hadoop-1.0.0 
export PATH=$PATH:$SQOOP_PREFIX/bin 
export FLUME_PREFIX=/home/itelligence/apache-flume-1.6.0-bin 
export PATH=$PATH:$FLUME_PREFIX/bin 

export CASSANDRA_PREFIX=/home/itelligence/apache-cassandra-2.0.8 
export PATH=$PAT4H:$CASSANDRA_PEFIX/bin 

后这个重新启动的.bashrc文件

source .bashrc 

如果问题仍然存在

型在终端下面,

/bin/cp /etc/skel/.bashrc ~/ 

它将取代您的损坏〜/。 bashrc与一个新鲜的。之后,你需要获取〜/ .bashrc中,使这一变化立即发生,在终端写,

source ~/.bashrc 
+0

由于您复制的最后一行中存在拼写错误,因此这仍然会与原始文件具有相同的影响... – twalberg