In practice, you should have an init script (i.e., an /etc/init.d/flume-ng script) that handles starting and stopping the agent. Same with everything else.
On 8 August 2014 14:37, Charles Robertson <charles.robert...@gmail.com> wrote: > When I tried running the agent thus: > > flume-ng agent -c /etc/flume/conf -f /etc/flume/conf/flume.conf -n > TwitterAgent & > > It still occupied the shell session without returning to the command, > although after closing the session window the logs do not show it shutting > down. > > 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 <na...@streamsets.com> wrote: > >> If you have sudo access, you can run a command as a particular user using >> sudo -u. >> >> `sudo -u flume flume-ng <config options> &` >> >> Also, if you installed Flume via RPM or Deb package, there should be an >> init.d script, though I'm not positive what user that script runs as. >> >> >> On Fri, Aug 8, 2014 at 9:08 AM, Babu, Prashanth < >> prashanth.b...@nttdata.com> wrote: >> >>> Or if you want to view the console from time to time, you can use >>> screen[1] or tmux[2] on Linux and launch Flume agent and leave it running >>> and detach from the console(s). >>> >>> >>> >>> Links: >>> >>> 1: http://www.gnu.org/software/screen >>> >>> 2: http://tmux.sourceforge.net >>> >>> >>> >>> >>> >>> *From:* Christopher Shannon [mailto:cshannon...@gmail.com] >>> *Sent:* 08 August 2014 14:32 >>> *To:* user@flume.apache.org >>> *Subject:* Re: Running an agent >>> >>> >>> >>> flume-ng blah blah & >>> runs in backround >>> >>> On Aug 8, 2014 8:19 AM, "Charles Robertson" <charles.robert...@gmail.com> >>> wrote: >>> >>> Hi all, >>> >>> I'm currently running my agent by ssh'ing in to the box and executing >>> the flume-ng agent command. >>> >>> This seems to have two effects (but please correct me if I have this >>> wrong): >>> >>> 1. It seems to run in the context of the ssh session, so if the >>> connection dies (from what I can understand from the logs) the agent shuts >>> down. It also means that session never returns to the command prompt. >>> >>> 2. It executes as the user I'm logged in as (which isn't the flume user.) >>> >>> So, my questions are: >>> >>> How can I run my agent in the background, without necessarily having to >>> be logged in? Also, how do I make it run as a specified user? (Although >>> this might be covered by the answer to the first.) >>> >>> Thanks, >>> Charles >>> >>> ______________________________________________________________________ >>> Disclaimer:This email and any attachments are sent in strictest >>> confidence for the sole use of the addressee and may contain legally >>> privileged, confidential, and proprietary data. If you are not the intended >>> recipient, please advise the sender by replying promptly to this email and >>> then delete and destroy this email and any attachments without any further >>> use, copying or forwarding >>> >> >> > -- Matt Sicker <boa...@gmail.com>
