Change the chkconfig script to 'nodetool eval' with inline erlang

for handling consult. Seems cleaner than having a couple of files
to handle a simple task - this is what we were trying to achieve
in Leeds.

rebar.config

@@ -84,7 +84,6 @@
          {template, "rel/files/riak-debug",        "bin/riak-debug"},
          {template, "rel/files/riak-chkconfig",    "bin/riak-chkconfig"},
          {template, "rel/files/riak-repl",         "bin/riak-repl"},
-         {template, "rel/files/check_riak_config", "bin/check_riak_config"},
 
          {copy, "rel/files/check_ulimit", "bin/hooks/prestart/check_ulimit"}
     ]},

rel/files/riak-chkconfig

@@ -8,5 +8,16 @@
 ## "vm.args = $VMARGS_PATH"
 ## "app.config = $CONFIG_PATH"
 
-$ERTS_DIR/bin/escript $RELEASE_ROOT_DIR/bin/check_riak_config $CONFIG_PATH
+CODE=" try
+           {ok, _} = file:consult(\"$CONFIG_PATH\"),
+           io:format(\"config is OK\\n\"),
+           halt(0)
+       catch
+           _:_ ->
+               io:format(\"Error reading ~p\\n\", [\"$CONFIG_PATH\"]),
+               halt(1)
+       end."
+
+$BINDIR/erl -noshell -boot start_clean -eval "$CODE"
+
 echo $CUTTLE_CONF