0
J'avais ajouté des instructions d'export pour Hcatalog dans mon fichier .bashrc qui a fini par gâcher mon fichier .basrc. Maintenant, même si j'ouvre le fichier bashrc dans mon cmd et supprime ces deux déclarations d'exportation, je ne suis toujours pas capable d'exécuter l'une des commandes.Les commandes ne fonctionnaient pas après l'édition du fichier bashrc dans ubuntu
Mon fichier actuel 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
Et l'erreur que je rencontre sont: hadoop namenode -format hadoop:command not found
Quelqu'un pourrait-il me s'il vous plaît aider. TIA.
J'ai vérifié mon bashrc, les déclarations d'exportation étaient déjà au besoin i .e dans les prochains llines. Mais j'ai reconnu une faute de frappe, remplacé le fichier basrc par défaut et il a commencé à travailler. Merci pour la réponse. –
la dernière ligne fait 'PATH =:/home/itelligence/apache-cassandra-2.0.0/bin', ce qui supprime toutes vos modifications précédentes à' PATH' - indice: quelle est la valeur de '$ PAT4H'? – twalberg