From: Dan Moore <dan@vaporwa.re>
To: unicorn-public@bogomips.org
Subject: SIGWINCH ignored...
Date: Tue, 19 May 2015 10:02:59 -0400 [thread overview]
Message-ID: <etPan.555b4293.5b47a5b7.e617@danbookpro> (raw)
I’m interested in the SIGWINCH signal and specifically the message that is posted to the console at an INFO level instead of DEBUG level: https://github.com/ddollar/foreman/issues/557 “INFO – : SIGWINCH ignored because we’re not daemonized” I would like to request that this be moved to DEBUG level as it’s quite chatty when using tmux, foreman, and terminal. I apologize if this was already discussed, but I cannot seem to perform a full search on the email archives.
next reply other threads:[~2015-05-19 23:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 14:02 Dan Moore [this message]
2015-05-19 23:28 ` SIGWINCH ignored Eric Wong
[not found] ` <861658785.98319.1432078146036.JavaMail.mobile-sync@ioii68>
2015-05-20 1:02 ` Dan Moore
2015-05-20 23:11 ` Eric Wong
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=etPan.555b4293.5b47a5b7.e617@danbookpro \
--to=dan@vaporwa.re \
--cc=unicorn-public@bogomips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://yhbt.net/unicorn.git/
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).