From: Zach Riggle <zachriggle@gmail.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Multios redirection while keeping current descriptors, and exec
Date: Tue, 10 May 2022 13:20:59 -0500 [thread overview]
Message-ID: <CAMP9c5mqbBiyW_Qo2cU-sn+TRhn6KE6WmJz9ujN=cPwTU2j1Pw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 456 bytes --]
Hello all!
Is there a simpler way to additionally log stdout/stderr to a file, while
keeping the existing one?
{ echo stdout; >&2 echo stderr } > /tmp/log > /dev/tty 2> /tmp/err
2>/dev/tty
Will log stdout to stdout and /tmp/log, for example.
Specifically, I want to be able to do this for the remainder of the process
via "exec". The goal is to have an interactive stdio like normal, but also
log all stdout / stderr to a log file.
*Zach Riggle*
[-- Attachment #2: Type: text/html, Size: 793 bytes --]
next reply other threads:[~2022-05-10 18:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 18:20 Zach Riggle [this message]
2022-05-10 18:49 ` John Covici
2022-05-10 18:54 ` Bart Schaefer
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='CAMP9c5mqbBiyW_Qo2cU-sn+TRhn6KE6WmJz9ujN=cPwTU2j1Pw@mail.gmail.com' \
--to=zachriggle@gmail.com \
--cc=zsh-users@zsh.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://git.vuxu.org/mirror/zsh/
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).