unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: Bill Lipa <dojo@masterleep.com>
Cc: unicorn-public@bogomips.org
Subject: Re: systemd with logs to journald
Date: Fri, 9 Sep 2016 22:23:13 +0000	[thread overview]
Message-ID: <20160909222313.GA24953@starla> (raw)
In-Reply-To: <CAKh11B42K1XRt-Tcd0VH4rOmVzd2W+p3k1RuLjCLayNjA0pvJA@mail.gmail.com>

Bill Lipa <dojo@masterleep.com> 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 :>

  reply	other threads:[~2016-09-09 22:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-09 22:16 systemd with logs to journald Bill Lipa
2016-09-09 22:23 ` Eric Wong [this message]
     [not found]   ` <CAKh11B7EFHq=zfvz0aej-bhKkvJyGwRxWRB3zjxOZejwERV3+A@mail.gmail.com>
2016-09-09 22:45     ` Eric Wong
2016-09-09 22:51       ` Bill Lipa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://yhbt.net/unicorn/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160909222313.GA24953@starla \
    --to=e@80x24.org \
    --cc=dojo@masterleep.com \
    --cc=unicorn-public@bogomips.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).