Bash ошибка синтаксиса около неожиданной лексемы newline

Страницы: [1]   Вниз

0 Пользователей и 1 Гость просматривают эту тему.

Страницы: [1]   Вверх

# /etc/bash/bashrc
#
# This file is sourced by all *interactive* bash shells on startup,
# including some apparently interactive shells such as scp and rcp
# that can't tolerate any output.  So make sure this doesn't display
# anything or bad things will happen !


# Test for an interactive shell.  There is no need to set anything
# past this point for scp and rcp, and it's important to refrain from
# outputting anything in those cases.
if [[ $- != *i* ]] ; then
        # Shell is non-interactive.  Be done now!
        return
fi

# Bash won't get SIGWINCH if another process is in the foreground.
# Enable checkwinsize so that bash will check the terminal size when
# it regains control.  #65623
# http://cnswww.cns.cwru.edu/~chet/bash/FAQ (E11)
shopt -s checkwinsize

# Disable completion when the input buffer is empty.  i.e. Hitting tab
# and waiting a long time for bash to expand all of $PATH.
shopt -s no_empty_cmd_completion

# Enable history appending instead of overwriting when exiting.  #139609
shopt -s histappend

# Save each command to the history file as it's executed.  #517342
# This does mean sessions get interleaved when reading later on, but this
# way the history is always up to date.  History is not synced across live
# sessions though; that is what `history -n` does.
# Disabled by default due to concerns related to system recovery when $HOME
# is under duress, or lives somewhere flaky (like NFS).  Constantly syncing
# the history will halt the shell prompt until it's finished.
#PROMPT_COMMAND='history -a'

# Change the window title of X terminals
case ${TERM} in
        [aEkx]term*|rxvt*|gnome*|konsole*|interix)
                PS1='[33]0;u@h:w07]'
                ;;
        screen*)
                PS1='[33ku@h:w33\]'
                ;;
        *)
                unset PS1
                ;;
esac

# Set colorful PS1 only on colorful terminals.
# dircolors --print-database uses its own built-in database
# instead of using /etc/DIR_COLORS.  Try to use the external file
# first to take advantage of user additions.
use_color=false
if type -P dircolors >/dev/null ; then
        # Enable colors for ls, etc.  Prefer ~/.dir_colors #64489
        LS_COLORS=
        if [[ -f ~/.dir_colors ]] ; then
                # If you have a custom file, chances are high that it's not the default.
                used_default_dircolors="no"
                eval "$(dircolors -b ~/.dir_colors)"
        elif [[ -f /etc/DIR_COLORS ]] ; then
                # People might have customized the system database.
                used_default_dircolors="maybe"
                eval "$(dircolors -b /etc/DIR_COLORS)"
        else
                used_default_dircolors="yes"
                eval "$(dircolors -b)"
        fi
        if [[ -n ${LS_COLORS:+set} ]] ; then
                use_color=true
        fi
        unset used_default_dircolors
else
        # Some systems (e.g. BSD & embedded) don't typically come with
        # dircolors so we need to hardcode some terminals in here.
        case ${TERM} in
        [aEkx]term*|rxvt*|gnome*|konsole*|screen|cons25|*color) use_color=true;;
        esac
fi

if ${use_color} ; then
        if [[ ${EUID} == 0 ]] ; then
                PS1+='[33[01;31m]h[33[01;34m] W $[33[00m] '
        else
                PS1+='[33[01;32m]u@h[33[01;34m] w $[33[00m] '
        fi

        alias ls='ls --color=auto'
        alias grep='grep --colour=auto'
        alias egrep='egrep --colour=auto'
        alias fgrep='fgrep --colour=auto'
else
        if [[ ${EUID} == 0 ]] ; then
                # show root@ when we don't have colors
                PS1+='u@h W $ '
        else
                PS1+='u@h w $ '
        fi
fi

for sh in /etc/bash/bashrc.d/* ; do
        [[ -r ${sh} ]] && source "${sh}"
done

# Try to keep environment pollution down, EPA loves us.
unset use_color sh

• 
• Forum
• The Ubuntu Forum Community
• Ubuntu Official Flavours Support
• New to Ubuntu
• [SOLVED] bash: syntax error near unexpected token `newline’

1. Hello all. I’m running Ubuntu Server and am having problems running a .sh script trying to build a Open GTS Server.

   the command is

   bin/initdb.sh -rootUser=<rootUser> -rootPass=<rootPass>

   The script is supposed to create a new mysql database. When i run the command i get..

   -bash: syntax error near unexpected token `newline’

   I’ve tried running it as sudo and my user and i get the same thing.

   tia

   ---

2. Re: bash: syntax error near unexpected token `newline’
   

   do root user or password contain the sequence n ?

   ---

3. Re: bash: syntax error near unexpected token `newline’
   

   Originally Posted by DaithiF
   

   do root user or password contain the sequence n ?

   No, there’s an n but no n in the rootUser / rootPass and just to be certain i changed the mysql root password to something without an n and got the same error.

   ---

4. Re: bash: syntax error near unexpected token `newline’
   

   Hmm … ok, wild guess, when it says

   Code:

   bin/initdb.sh -rootUser=<rootUser> -rootPass=<rootPass>

   are you typing:

   Code:

   bin/initdb.sh -rootUser=<rootUser> -rootPass=<rootPass>

   or

   Code:

   bin/initdb.sh -rootUser=rootUser -rootPass=rootPass

   (its the second one that you need — the angle brackets are there as placeholders, they’re not meant to be typed)

   ---

5. Re: bash: syntax error near unexpected token `newline’
   

   Originally Posted by DaithiF
   

   Hmm … ok, wild guess, when it says

   Code:

   bin/initdb.sh -rootUser=<rootUser> -rootPass=<rootPass>

   are you typing:

   Code:

   bin/initdb.sh -rootUser=<rootUser> -rootPass=<rootPass>

   or

   Code:

   bin/initdb.sh -rootUser=rootUser -rootPass=rootPass

   (its the second one that you need — the angle brackets are there as placeholders, they’re not meant to be typed)

   doh! taking out the angle brackets did it.

   thanks!

   ---

6. Re: bash: syntax error near unexpected token `newline’
   

   ---