The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Nuno Silva <nuno.silva@vgertech.com>
To: gene.heskett@verizon.net, linux-kernel@vger.kernel.org
Subject: Re: ANother debugging Q
Date: Wed, 14 Jan 2004 01:01:47 +0000	[thread overview]
Message-ID: <400494FB.7040709@vgertech.com> (raw)
In-Reply-To: <200401131817.44856.gene.heskett@verizon.net>



Gene Heskett wrote:
> Unforch, that seems to shut down the opening of the error advisory 
> window.  It just sits there showing a blank (data wise) screen. And 
> extensive scrolling back thru about 5 megs of the output doesn't 
> disclose a missing file that I can see.  How would I go about 
> redirecting that output to grep, it seems to bypass an
> 
>  "strace -f ksysguard|grep open"
> 

Do "man strace" again :-)

Then see the -o option or the -e option.

(Or "man bash" and read about output redirection 2>&1 )

Regards,
Nuno Silva


  reply	other threads:[~2004-01-14  0:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-13 17:43 ANother debugging Q Gene Heskett
2004-01-13 17:56 ` Muli Ben-Yehuda
2004-01-13 23:17   ` Gene Heskett
2004-01-14  1:01     ` Nuno Silva [this message]
2004-01-14  3:16       ` Gene Heskett

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=400494FB.7040709@vgertech.com \
    --to=nuno.silva@vgertech.com \
    --cc=gene.heskett@verizon.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox