On 18 Nov 2001, Joerg Schilling wrote: > First: t makes no sense to do timings with compressed archives > where tar has to call e.g. gzip to decompress the archive while > running.
I realized that when I did the test: I just wanted to show that the problem exists also when calling gzip / bzip2. That's all... > Second: From reading further down, it turns out that you did the > test on a "tiny" machine as it has been used about 12-14 years > ago. In former times, star used to use 1 MB for FIFO by default. > A few weeks ago, I decided to increase FIFO size for what I > assume is a "modern machine". Now, star uses 1 MB (as before) on > sun3 machines, 4 MB on Linux (as Linux detected mmap() a few > months before and SYSV shared mem is static and limited) and 8 MB > on all other machines. This usually dramatically speeds up > things. You are hit by the way Linux does memory management. If > Linux (with the old memory concept - I did not yet test the new > one) has less than 8 MB of free memory, it becomes very very > slow. If you run star as root there is a second change (made a > few weeks ago) that is intended to speed up operation: It tries > to lock the FIFO in memory. > > On your specific machine the last two changes seem to hurt you > but note that this cannot be called typical behaviour. The tests _were_ run as root, and top reports ~11MB free before using star. So, what are the problems affecting me? > There are plans to add a way to specify the default FIFO size in > /etc/default/star Note that backup speed with a DLT tape may > increase by more than 10% if you use 128 MB for the FIFO. > However, I won't recommend to use more than 1/4 of the total free > memory of the machine. Is there a way I can set this _now_ as a compile-time option? I have no problems with doing that. Can I also test another version of star? > >2. There are several cool things in GNU tar that don't work in > >star. Here's a list: > > options :: star equivalent > > o -cf :: -c -f > > o -xf :: -x -f > > o -C /fubar :: -C=/fubar > > It seems that you did not read the man pages well enough... > Neither GNUtar not star list that you may combine single char > BOOLEAN flags but both support them. > > So what is your problem? I didn't know whether or not this was a unintended side effect. I want to be able to use the same options for star as I do for GNU tar (i.e. I wish I could use "-xf" in star like I do in GNU tar; I wish I could use "-C /tmp" in star like I do in GNU tar). I apologize for being so valuge in my previous message. > >3. Is there a way to remove files from tar archives using star? > > NO, never needeed So what do I do? [ star -x -f file.tar -C=./dir; rm -f ./dir/fubar; rm -f file.tar; star -c -f file.tar ./dir; rm -rf ./dir ]? > >4. I noticed the following files are installed when 'make > >install'ing Schilling programs: > > >/usr/include/align.h > >/usr/include/avoffset.h > >/usr/lib/libdeflt.a > >/usr/lib/libfile.a > >/usr/lib/libhfs.a > >/usr/lib/librscg.a > >/usr/lib/libscg.a > >/usr/lib/libschily.a > >/usr/lib/libunls.a > > Well, you usually don't need them. So I guess it would be OK to not distribute them period, I guess. -- Karol Pietrzak PGP KeyID: 3A1446A0 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
