首页
学习
活动
专区
圈层
工具
发布
社区首页 >问答首页 >使用sudo作为用户运行"sudo -s“,不提供.bashrc源。

使用sudo作为用户运行"sudo -s“,不提供.bashrc源。
EN

Unix & Linux用户
提问于 2021-12-14 16:10:40
回答 1查看 236关注 0票数 2

我希望能够使用sudo作为用户运行sudo -s,并有/root/..bashrc源代码。我检查了.bashrc文件和/root的.profile文件,两者看起来都很好。

每次我尝试将sudo -s作为用户使用时,都不会使用.bashrc。在运行sudo -i时,.bashrc是源。

为什么.bashrc不是sudo -s的源,而是sudo -i的源?

据我所知,在部署之后,我没有在/root/..bashrc或/root/..profile中更改任何内容。

/root/..profile

代码语言:javascript
复制
# ~/.profile: executed by Bourne-compatible login shells.

if [ "$BASH" ]; then
  if [ -f ~/.bashrc ]; then
    . ~/.bashrc
  fi  
fi

mesg n 2> /dev/null || true

/root/..bashrc

代码语言:javascript
复制
# ~/.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 in the history. See bash(1) for more options
# ... or force ignoredups and ignorespace
HISTCONTROL=ignoredups:ignorespace

# 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

# 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\]\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

# some more ls aliases
alias ll='ls -alF'
alias la='ls -A'
alias l='ls -CF'

# 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

<#>更新:

我解决了问题。首先,.bashrc文件一直都是源源不断的,我只是认为它不是因为没有颜色被应用到终端会话。为了重新添加颜色,我需要调整.bashrc文件中引起问题的部分。

问题段

代码语言:javascript
复制
    xterm-color) color_prompt=yes;;

更改为:

代码语言:javascript
复制
    xterm-color|*-256color) color_prompt=yes;;
EN

回答 1

Unix & Linux用户

发布于 2021-12-14 18:14:45

sudo -s在没有命令的情况下运行(例如,sudo -s ls)会启动一个交互式的shell。sudo -i启动一个登录shell,它来源于所有标准的登录外壳rc文件--.profile.bash_login

所以一切都正常运作。我经常使用sudo -s,因为我不想将当前目录更改为根用户的主目录。

但是,如果您不想使用sudo -i,那么sudo -s bash -l应该可以工作。bash -l启动一个登录shell。

票数 0
EN
页面原文内容由Unix & Linux提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接:

https://unix.stackexchange.com/questions/681437

复制
相关文章

相似问题

领券
问题归档专栏文章快讯文章归档关键词归档开发者手册归档开发者手册 Section 归档