On Monday 12 March 2007, Douglas McNaught wrote: >Gene Heskett <[EMAIL PROTECTED]> 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! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
