public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gene Heskett <gene.heskett@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Douglas McNaught <doug@mcnaught.org>,
	Con Kolivas <kernel@kolivas.org>,
	amanda-hackers@amanda.org, Matt Mackall <mpm@selenic.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	ck@vds.kolivas.org
Subject: Re: RSDL for 2.6.21-rc3- 0.29
Date: Mon, 12 Mar 2007 14:28:29 -0400	[thread overview]
Message-ID: <200703121428.29947.gene.heskett@gmail.com> (raw)
In-Reply-To: <873b4alj52.fsf@suzuka.mcnaught.org>

On Monday 12 March 2007, Douglas McNaught wrote:
>Gene Heskett <gene.heskett@gmail.com> writes:
>> If, and I have previously, I revert to a 2.6.20-ck1 patching, this
>> does not occur.  So my contention is that someplace in this recent
>> progression from 2.6.20 to 2.6.21-rc3, there is a patch which acts to
>> change how c-time is being reported to tar.  Or there is a spillage
>> into c-times when tar does its estimate scans where the output goes to
>> /dev/null. Or possibly even this version of tar is doing it
>> differently.  I just looked up how to get the c-times out of ls, and
>> they, as far as ls is concerned, look sane.  But tars actions while
>> running a 2.6.21-rcX kernel certainly are not.  I do have a plain -rc2
>> I can try, so that will be the next test.  If that also fails in this
>> manner, I'll build a later 2.6.20-2 or whatever to verify that it
>> doesn't so suffer.
>
>You may find 'strace' useful to track down this sort of thing (though
>the output can be voluminous).
>
>-Doug

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.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
I'm definitely not in Omaha!

  reply	other threads:[~2007-03-12 18:28 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 [this message]
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
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=200703121428.29947.gene.heskett@gmail.com \
    --to=gene.heskett@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=amanda-hackers@amanda.org \
    --cc=ck@vds.kolivas.org \
    --cc=doug@mcnaught.org \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    /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