On Wed, Mar 5, 2008 at 6:16 AM, Andrew Sackville-West
<[EMAIL PROTECTED]> wrote:
> On Mon, Mar 03, 2008 at 08:08:47PM -0800, joseph lockhart wrote:
> >
> > Luis Maceira <[EMAIL PROTECTED]> wrote: How can I see all the messages
> generated by
> > a bash command (configure make make install,
> >
On Mon, Mar 03, 2008 at 08:08:47PM -0800, joseph lockhart wrote:
>
> Luis Maceira <[EMAIL PROTECTED]> wrote: How can I see all the messages
> generated by
> a bash command (configure make make install,
> for example) to standard output(computer screen),
> and at the same time make sure that all i
It's my fault.
I mistake something like this
exec 6>&1 1>&-
echo "To a closed fd"
Kumar Appaiah wrote:
On Tue, Mar 04, 2008 at 12:10:25PM +0800, hhding wrote:
Any method to redirect any fd to the pipe?
Not only stdout,stderr.
If you mean both stdout and stderr
./configure 2>&1 | tee
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
joseph lockhart wrote:
> Luis Maceira <[EMAIL PROTECTED]> wrote: How can I see all the messages
> generated by
> a bash command (configure make make install,
> for example) to standard output(computer screen),
> and at the same time make sure that all
On Tue, Mar 04, 2008 at 12:10:25PM +0800, hhding wrote:
> Any method to redirect any fd to the pipe?
> Not only stdout,stderr.
If you mean both stdout and stderr
./configure 2>&1 | tee log.txt
would work. But I don't know if that is what you meant.
HTH.
Kumar
--
Kumar Appaiah,
458, Jamuna Hos
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hhding wrote:
> Any method to redirect any fd to the pipe?
> Not only stdout,stderr.
>
> Chris Henry wrote:
>> Hi,
>> You can use tee. e.g. ./configure | tee filename
>>
>> Chris
>>
>> On Tue, Mar 4, 2008 at 11:33 AM, Luis Maceira
>> <[EMAIL PROTECTED
Any method to redirect any fd to the pipe?
Not only stdout,stderr.
Chris Henry wrote:
Hi,
You can use tee. e.g. ./configure | tee filename
Chris
On Tue, Mar 4, 2008 at 11:33 AM, Luis Maceira <[EMAIL PROTECTED]> wrote:
How can I see all the messages generated by
a bash command (configure m
Luis Maceira <[EMAIL PROTECTED]> wrote: How can I see all the messages
generated by
a bash command (configure make make install,
for example) to standard output(computer screen),
and at the same time make sure that all is
written to a text file for later analysis.
It is a redirection but I don´t
On Mon, Mar 03, 2008 at 07:33:20PM -0800, Luis Maceira wrote:
> How can I see all the messages generated by
> a bash command (configure make make install,
> for example) to standard output(computer screen),
> and at the same time make sure that all is
> written to a text file for later analysis.
>
On Mon, Mar 03, 2008 at 07:33:20PM -0800, Luis Maceira wrote:
> How can I see all the messages generated by
> a bash command (configure make make install,
> for example) to standard output(computer screen),
> and at the same time make sure that all is
> written to a text file for later analysis.
>
On Mon, Mar 03, 2008 at 07:33:20PM -0800, Luis Maceira wrote:
> How can I see all the messages generated by
> a bash command (configure make make install,
> for example) to standard output(computer screen),
> and at the same time make sure that all is
> written to a text file for later analysis.
>
Hi,
You can use tee. e.g. ./configure | tee filename
Chris
On Tue, Mar 4, 2008 at 11:33 AM, Luis Maceira <[EMAIL PROTECTED]> wrote:
> How can I see all the messages generated by
> a bash command (configure make make install,
> for example) to standard output(computer screen),
> and at the same
How can I see all the messages generated by
a bash command (configure make make install,
for example) to standard output(computer screen),
and at the same time make sure that all is
written to a text file for later analysis.
It is a redirection but I don´t know how to make
both things happen at the
13 matches
Mail list logo
