Mailing-List: contact dev-help@aurora.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aurora.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <541AE6E0.4000408@blue-yonder.com>
References: <541AE6E0.4000408@blue-yonder.com>
Date: Thu, 18 Sep 2014 08:30:29 -0700
Message-ID: 
 <CAGRA8uP8u3kpN3g_g8LMwzGfKGZjU8c7Mev8S-Gx0O0LeWg-kA@mail.gmail.com>
Subject: Re: Log to disk
From: Bill Farner <wfarner@apache.org>
To: "dev@aurora.incubator.apache.org" <dev@aurora.incubator.apache.org>
Content-Type: multipart/alternative; boundary=f46d04428dea172d18050358aa52

--f46d04428dea172d18050358aa52
Content-Type: text/plain; charset=UTF-8

Unfortunately, that log_dir argument comes from a third-party library, and
doesn't do what you want (i'd happily accept a bug to remove it, as it's
irrelevant to us).

The best way is to pipe stderr and stdout to a file, and let logrotate deal
with that file.  A big upside to this approach is that you can use this
strategy for all your applications*.


* not all applications handle SIGHUP cleanly, so there are gotchas


-=Bill

On Thu, Sep 18, 2014 at 7:06 AM, Stephan Erb <stephan.erb@blue-yonder.com>
wrote:

> Hi,
>
> is there a way to tell Aurora to log to disk? The documented parameters
> (see aurora-scheduler --help) seem to do nothing.
>
> AURORA_FLAGS=(
>   ...
>   -vlog=INFO
>   -log_dir=/var/log/aurora
> )
>
> Thanks,
> Stephan
>

--f46d04428dea172d18050358aa52--