Php Ubuntu导出/opt/lampp/lampp到路径

我试图把lampp放到我的Ubuntu路径中，但我似乎做错了什么，因为它不起作用

我将其放入~/.bashrc文件中：

export PATH="/opt/lampp/lampp:$PATH"

然后我在~中运行了以下命令： $source.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
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

### Added by the Heroku Toolbelt
export PATH="/usr/local/heroku/bin:$PATH"
export PATH="/opt/lampp/lampp:$PATH"

---

好吧，我想我知道发生了什么！将

~/.bashrc

中的

$PATH

行更改为以下内容：

export PATH="/opt/lampp:$PATH"

然后尝试

source~/.bashrc

，或者打开一个新的终端。您现在应该可以使用

lampp

和

xampp

命令。两者都应该做同样的事情

问题是

$PATH

变量指向包含可执行文件的目录，而不是直接指向可执行文件。似乎

/opt/lampp/lampp

是指向可执行文件

/opt/lampp/xampp

的符号链接

---

---

更新：当您使用

sudo

时，出于安全原因，它可能不尊重您的

$PATH

变量。您可以尝试运行

sudo visudo

，并编辑写有

Defaults secure_path=“…”

的行以包含

/opt/lampp

。然后

sudo lampp start

应该可以工作了

好吧，我想我知道发生了什么事！将

~/.bashrc

中的

$PATH

行更改为以下内容：

export PATH="/opt/lampp:$PATH"

然后尝试

source~/.bashrc

，或者打开一个新的终端。您现在应该可以使用

lampp

和

xampp

命令。两者都应该做同样的事情

问题是

$PATH

变量指向包含可执行文件的目录，而不是直接指向可执行文件。似乎

/opt/lampp/lampp

是指向可执行文件

/opt/lampp/xampp

的符号链接

---

---

更新：当您使用

sudo

时，出于安全原因，它可能不尊重您的

$PATH

变量。您可以尝试运行

sudo visudo

，并编辑写有

Defaults secure_path=“…”

的行以包含

/opt/lampp

。然后

sudo lampp start

应该可以工作了

你能发布你的

~/.bashrc

的内容吗？我编辑了这篇文章：）让我们做一个健康检查。将

echo$PATH

添加到

~/.bashrc

的末尾，然后运行

source~/.bashrc

。你应该看到一条长长的路线。是吗？是的，它返回给我这个：/opt/lampp/lampp:/usr/local/heroku/bin:/opt/lampp/lampp:/usr/local/heroku/bin:/usr/local/sbin:/usr/sbin:/usr/bin:/sbin:/usr/games:/usr/local/games:/snap/bin:/usr/lib/jvm/java-8-oracle/bin:/usr/lib/java-8-oracle/db/bin:/usr/lib/jre/jre/lright，因此，

$PATH

设置正确。您可以从

~/.bashrc

中删除最后一行。接下来，运行以下命令：

ls-l/opt/lampp/lampp | curl-F'sprunge=你能发布你的
~/.bashrc
的内容吗？我编辑了这篇文章：）让我们做一个健康检查。将
echo$PATH
添加到
~/.bashrc
的末尾，然后运行
source~/.bashrc
。你应该看到一条长长的路线。是吗？是的，它返回给我这个：/opt/lampp/lampp:/usr/local/heroku/bin:/opt/lampp/lampp:/usr/local/heroku/bin:/usr/local/sbin:/usr/sbin:/usr/bin:/sbin:/usr/games:/usr/local/games:/snap/bin:/usr/lib/jvm/java-8-oracle/bin:/usr/lib/java-8-oracle/db/bin:/usr/lib/jre/jre/lright，因此，
$PATH
设置正确。您可以从
~/.bashrc
中删除最后一行。接下来，运行以下命令：
ls-l/opt/lampp/lampp | curl-F'sprunge=sudo lampp start（我也尝试过sudo xampp start，但结果相同）sudo lampp start（我也尝试过sudo xampp start，但结果相同）没有一行说“defaults secure_path”sudo lampp start（我也尝试过sudo xampp start，但结果相同）没有一行说“defaults secure_path”