When I tried running the agent thus:
flume-ng agent -c /etc/flume/conf -f /etc/flume/conf/flume.conf -n
It still occupied the shell session without returning to the command,
although after closing the session window the logs do not show it shutting
Is this how you would run a flume agent in practice, or should I be looking
to use something like oozie or other workflow or scheduler type application
to kick it off?
On 8 August 2014 17:51, Jonathan Natkins <[EMAIL PROTECTED]> wrote: