Re: RSDL for 2.6.21-rc3- 0.29

[Patrick Mau <mau@oscar.ping.de>]

On Mon, Mar 12, 2007 at 03:43:09PM -0400, Douglas McNaught wrote:
> 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.

Hi,

I hope you don't mind me jumping in ...

Why not temporarly replace "/bin/tar" with a shell script that does:

#!/bin/sh
exec strace -f -o output /bin/real.tar $@

That should be working, shouldn't it ?

Cheers,
Patrick