From: Bill Davidsen <davidsen@tmr.com>
To: Arijit Das <Arijit.Das@synopsys.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Does Linux has File Stream mapping support...?
Date: Fri, 18 Nov 2005 14:06:51 -0500 [thread overview]
Message-ID: <437E264B.8070609@tmr.com> (raw)
In-Reply-To: <7EC22963812B4F40AE780CF2F140AFE920906A@IN01WEMBX1.internal.synopsys.com>
Arijit Das wrote:
> Ye...I know of tee.
>
> But the issue here is I have a HUGE Compiler (an Simulation tool) in which thousands of places there are "printf" statements to print messages to STDOUT stream. Now, a requirement came up which needs all those messages thrown to STDOUT also to be logged in a LOGFILE (in addition to STDOUT). Yes, this can be done through tee...but the usage model of the compiler doesn't leave that possibility open for me.
>
> So, am looking for a solution inside the Compiler code.
1 - using script allows stdout and file capture, might help
2 - redirect to a fifo, hang tee off the fifo
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
next prev parent reply other threads:[~2005-11-18 19:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 12:51 Does Linux has File Stream mapping support...? Arijit Das
2005-11-18 12:59 ` Bas Westerbaan
2005-11-18 13:01 ` Bas Westerbaan
2005-11-18 14:28 ` Dick Streefland
2005-11-18 19:06 ` Bill Davidsen [this message]
2005-11-18 19:39 ` Lennart Sorensen
2005-11-21 9:18 ` Jim Nance
[not found] <5abPs-7Da-41@gated-at.bofh.it>
2005-11-18 12:30 ` Bodo Eggert
-- strict thread matches above, loose matches on Subject: below --
2005-11-18 10:38 Arijit Das
2005-11-18 20:14 ` James Courtier-Dutton
2005-11-18 20:41 ` linux-os (Dick Johnson)
2005-11-19 4:27 ` Herbert Xu
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=437E264B.8070609@tmr.com \
--to=davidsen@tmr.com \
--cc=Arijit.Das@synopsys.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.