From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00 shortcircuit=no autolearn=ham autolearn_force=no version=3.4.0 Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 9C3E1207DF; Fri, 9 Sep 2016 22:23:13 +0000 (UTC) Date: Fri, 9 Sep 2016 22:23:13 +0000 From: Eric Wong To: Bill Lipa Cc: unicorn-public@bogomips.org Subject: Re: systemd with logs to journald Message-ID: <20160909222313.GA24953@starla> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: List-Id: Bill Lipa wrote: > Hello, > > Is there a recommended way to run unicorn under systemd and get its > stdout/err to go to journald rather than into a file on disk? I > prefer to minimize the number of places I have to look for errors. Remove the stdout_path and stderr_path directives from the config file. unicorn won't change stdout/stderr by default, so journald should pick up anything that goes there. Admittedly, I haven't gotten around to trying journald, just systemd + syslog. That combo handles stdout/stderr fine. > Thank you! No problem :>