Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

r6633 breaks server.sh [moved] #1071

Closed
lvca opened this issue Dec 10, 2012 · 0 comments
Closed

r6633 breaks server.sh [moved] #1071

lvca opened this issue Dec 10, 2012 · 0 comments

Comments

@lvca
Copy link
Member

lvca commented Dec 10, 2012

This is Issue 1071 moved from a Google Code project.
Added by 2012-09-25T09:38:26.000Z by t.broyer.
Please review that bug for more context and additional comments, but update this bug.
Closed (Fixed).

Original labels: Type-Defect, Priority-Medium, v1.2.0

Original description

<b>OrientDB release? (If you're using a SNAPSHOT please attach also the build</b>
number found in &quot;build.number&quot; file):
1.2.0-20120924.234740-36

<b>What steps will reproduce the problem?</b>
&quot;service orientdb start&quot;
with /etc/init.d/orientdb being a symlink to /opt/orientdb/bin/orientdb.sh
On CentOS 5.7; root's $SHELL being /bin/bash

<b>What is the expected output? What do you see instead?</b>
Server won't start.
orientdb.err says:
./server.sh: line 53: syntax error near unexpected token `else'
./server.sh: line 53: `else'

The issue is the following snippet in server.sh:
if [ -b &quot;${CONFIG_FILE}&quot; ]
then
else
  CONFIG_FILE=$ORIENTDB_HOME/config/orientdb-server-config.xml
fi

It should rather be:
if [ ! -b &quot;${CONFIG_FILE}&quot; ]
then
  CONFIG_FILE=$ORIENTDB_HOME/config/orientdb-server-config.xml
fi
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant