☰

"시작 프로그램 창"의 .sh 파일 내에서 실행할 때 scp 및 rsync가 작동하지 않습니다.

tag-icon • tag-icon ubuntu ssh startup scp
"시작 프로그램 창"의 .sh 파일 내에서 실행할 때 scp 및 rsync가 작동하지 않습니다.

my_backup.shUbuntu Mate 16.04에는 다음과 같은 파일이 있습니다 .

# Log just for trying 
echo $(date) >> /home/albert/dia_hora

# BBDD
NOW=$(date --date="yesterday" +"%d")
FILE="cavecanem_production_$NOW.sql"
scp [email protected]:/home/rails/backup/$FILE /home/albert/druby/copies/cavecanem/bbdd

# Fitxers
rsync -r --ignore-existing [email protected]:/home/rails/cavecanem/public/fitxers/ /home/albert/druby/copies/cavecanem/public

그것은로 구성됩니다

  1. dia_hora 파일에 날짜/시간 로그 저장(올바르게 작동)
  2. scp로 복사(시작 프로그램에서는 작동하지 않음)
  3. rsync로 복사(시작 프로그램에서는 작동하지 않음)

터미널에서 실행하면 sh /home/albert/my_backup.sh 모든 것올바르게 작동합니다(1,2,3개 부품).

하지만 시작 프로그램 창에 다음과 같은 작업을 넣으면:sh /home/albert/my_backup.sh 오직첫 번째 부분을 실행합니다(echo $(날짜) >> /home/albert/dia_hora)

"시작 프로그램"에서 scp 또는 rsync를 실행할 수 없는 이유는 무엇입니까?

5월 22일에 수정됨: 문제는 scp, rsync를 실행하려면 먼저 .bashrc를 실행해야 하고 시작 순서가 다음과 같다는 점입니다.

  1. .프로필
  2. 시작 프로그램(우분투 창, 즉 scp 및 rsync)
  3. .baschrc

감사해요

카탈로니아어로 된 스크린샷(죄송합니다)

여기에 이미지 설명을 입력하세요

내 .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

export PATH="$PATH:$HOME/.rvm/bin" # Add RVM to PATH for scripting

cd $HOME/druby/cavecanem
export LANGUAGE='en_US.UTF-8 git'

내 .profile 파일:

# ~/.profile: executed by the command interpreter for login shells.
# This file is not read by bash(1), if ~/.bash_profile or ~/.bash_login
# exists.
# see /usr/share/doc/bash/examples/startup-files for examples.
# the files are located in the bash-doc package.

# the default umask is set in /etc/profile; for setting the umask
# for ssh logins, install and configure the libpam-umask package.
#umask 022

# if running bash
if [ -n "$BASH_VERSION" ]; then
    # include .bashrc if it exists
    if [ -f "$HOME/.bashrc" ]; then
    . "$HOME/.bashrc"
    fi
fi

# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
    PATH="$HOME/bin:$PATH"
fi

export PATH="$PATH:$HOME/.rvm/bin" # Add RVM to PATH for scripting

[[ -s "$HOME/.rvm/scripts/rvm" ]] && source "$HOME/.rvm/scripts/rvm" # Load RVM into a shell session *as a function*

관련 정보