From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: metalog: fix bleeding logs onto tty1
Date: Mon, 21 Aug 2023 17:45:00 +0200 [thread overview]
Message-ID: <20230821154500.FcMhpg4MQ71QX7aqOEtf0XV1Vrf1v5ZfdA2crUj6DW0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45700@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 681 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/pull/45700#issuecomment-1686577804
Comment:
> I think running it as deamon should fix the tty problem. Just add `-B` option.
No runit services are required to run in the foreground.
Just removing this line is probably not the right solution, output redirected to `stdout` will be written to the commandline of the `runsvdir` process as fallback logging mechanism.
This fallback mechanism shouldn't be used as general logging target where everything is logged to, its already bad user experience, but duplicating all syslog messages into it just makes it even more useless.
next prev parent reply other threads:[~2023-08-21 15:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 8:47 [PR PATCH] " shahab-vahedi
2023-08-21 11:46 ` [PR PATCH] [Updated] " shahab-vahedi
2023-08-21 15:36 ` aryandb
2023-08-21 15:39 ` aryandb
2023-08-21 15:45 ` Duncaen [this message]
2023-08-21 18:15 ` shahab-vahedi
2023-08-21 18:26 ` Duncaen
2023-08-21 18:32 ` shahab-vahedi
2023-08-21 18:34 ` [PR PATCH] [Updated] " shahab-vahedi
2023-08-21 18:34 ` shahab-vahedi
2023-08-21 18:45 ` Duncaen
2023-08-21 18:47 ` Duncaen
2023-08-21 19:01 ` aryandb
2023-08-21 19:50 ` [PR PATCH] [Updated] " shahab-vahedi
2023-08-21 19:51 ` shahab-vahedi
2023-08-26 20:21 ` shahab-vahedi
2023-08-31 11:57 ` shahab-vahedi
2023-08-31 14:09 ` [PR PATCH] [Merged]: " Duncaen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230821154500.FcMhpg4MQ71QX7aqOEtf0XV1Vrf1v5ZfdA2crUj6DW0@z \
--to=duncaen@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).