flume-ng script accepts the parameter conf to pass the directory which stores the configuration files and adds it to the FLUME_CLASSPATH. But org.apache.flume.node.Application expects configuration files passed to have an absolute path. So even if user passes `conf` and `conf-file` option, `application` looks for the configuration file in the directory from which it is executed. It would be good to take the `conf` value into consideration so that users can place the config files anywhere.
Currently big-top init.d script joins the `conf` and `conf-file` values when calling flume-ng. The same can be done in the ` flume-ng ` script. Alternatively the `conf ` parameter can be read in ` application ` and concatenated in the code. The latter is a cleaner approach but will have impact on ` big-top `.