public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Douglas McNaught <doug@mcnaught.org>
To: Gene Heskett <gene.heskett@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RSDL for 2.6.21-rc3- 0.29
Date: Mon, 12 Mar 2007 15:43:09 -0400	[thread overview]
Message-ID: <87slcajliq.fsf@suzuka.mcnaught.org> (raw)
In-Reply-To: <200703121510.18268.gene.heskett@gmail.com> (Gene Heskett's message of "Mon, 12 Mar 2007 15:10:18 -0400")

Gene Heskett <gene.heskett@gmail.com> writes:

> On Monday 12 March 2007, Douglas McNaught wrote:
>>Gene Heskett <gene.heskett@gmail.com> writes:
>>> I'd considered it, but with 32 dle entries, the whole strace output
>>> would be terrabytes & I don't have THAT much disk.  Not to mention it
>>> traces only the parent process, so tar would be merrily marching along
>>> to its own drummer and not traced I'm  afraid.
>>
>>$ strace -ff
>>
>>-Doug
>
> Someone else suggested the single -f, and I tried that, but even with the 
> shell history set for 100,000 lines, i can't get back to the start, and I 
> think its mucking with the shell arguments numbering as what I can see is 
> about 5 reads through /etc/services accompanied by endless complaints 
> of -EBADFD, the the logfile it generates says the port it was given was 
> rejected when amcheck was run, here is that snip:

I'd do 'strace -ff -o /tmp/amanda-strace <command>', which will give
you a set of files in /tmp, one for each PID created by fork().  Then
find the one that has the 'tar' invocation you're looking for.

-Doug

  parent reply	other threads:[~2007-03-12 19:43 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-11  1:35 RSDL-mm 0.28 Matt Mackall
2007-03-11  2:28 ` Con Kolivas
2007-03-11  3:16   ` Andrew Morton
2007-03-11  3:43     ` William Lee Irwin III
2007-03-11  3:59     ` Con Kolivas
2007-03-11  3:39       ` Andrew Morton
2007-03-11  3:44         ` Con Kolivas
2007-03-11  4:01   ` Matt Mackall
2007-03-11  4:03     ` Matt Mackall
2007-03-11  6:19       ` Con Kolivas
2007-03-12  5:38         ` RSDL for 2.6.21-rc3- 0.29 Gene Heskett
2007-03-12  5:48           ` Con Kolivas
2007-03-12  6:37             ` Gene Heskett
2007-03-12 10:04               ` Gene Heskett
2007-03-12 12:51                 ` Douglas McNaught
2007-03-12 18:28                   ` Gene Heskett
2007-03-12 18:46                     ` Douglas McNaught
2007-03-12 19:10                       ` Gene Heskett
2007-03-12 19:14                         ` Lee Revell
2007-03-12 19:43                         ` Douglas McNaught [this message]
2007-03-12 19:54                           ` Patrick Mau
2007-03-12 20:24                             ` Gene Heskett
2007-03-13  1:32                             ` Stracing Amanda (was: RSDL for 2.6.21-rc3- 0.29) Douglas McNaught
2007-03-13  2:39                               ` Gene Heskett
2007-03-13  3:01                                 ` Nish Aravamudan
2007-03-13  4:04                                   ` Gene Heskett
2007-03-13  4:45                                     ` Willy Tarreau
2007-03-13  5:48                                       ` Gene Heskett
2007-03-12 13:22   ` RSDL-mm 0.28 David Schwartz
2007-03-12 14:54     ` Ray Lee
2007-03-13  7:22     ` Nick Piggin
2007-03-11  7:32 ` Willy Tarreau

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=87slcajliq.fsf@suzuka.mcnaught.org \
    --to=doug@mcnaught.org \
    --cc=gene.heskett@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox