Is this perl poblem?

[Marshall Dudley]

When exec is used to shell tar, and tar is piped back to stdout, after
the apache timeout, if the download is cancelled, tar locks up and uses
100% of the free cpu time.

I have posted the problem in several forums, but cannot get any ideas on
it. At this point I don't know if this is an Apache problem, FreeBSD
core problem, gtar problem or perl problem.

Code line is:

exec("/usr/bin/tar cflz - $store_path
/home/kingcart/html/store/$username");

Anyone have any ideas on at least program/system I should be working on
to try and resolve this?

Thanks,

Marshall

[Jürgen Exner]

Marshall Dudley wrote:

> When exec is used to shell tar, and tar is piped back to stdout, after
> the apache timeout, if the download is cancelled, tar locks up and
> uses 100% of the free cpu time.
>
> I have posted the problem in several forums, but cannot get any ideas
> on it. At this point I don't know if this is an Apache problem,
> FreeBSD core problem, gtar problem or perl problem.
>
> Code line is:
>
> exec("/usr/bin/tar cflz - $store_path
> /home/kingcart/html/store/$username");
>
> Anyone have any ideas on at least program/system I should be working
> on to try and resolve this?

Have you tried using Archive::Tar instead of shelling out to /usr/bin/tar?

jue

[Marshall Dudley]

No, but I will research it.

Thanks,

Marshall

"Jürgen Exner" wrote:

> Marshall Dudley wrote:

> > When exec is used to shell tar, and tar is piped back to stdout, after
> > the apache timeout, if the download is cancelled, tar locks up and
> > uses 100% of the free cpu time.
> >
> > I have posted the problem in several forums, but cannot get any ideas
> > on it. At this point I don't know if this is an Apache problem,
> > FreeBSD core problem, gtar problem or perl problem.
> >
> > Code line is:
> >
> > exec("/usr/bin/tar cflz - $store_path
> > /home/kingcart/html/store/$username");
> >
> > Anyone have any ideas on at least program/system I should be working
> > on to try and resolve this?

>
> Have you tried using Archive::Tar instead of shelling out to /usr/bin/tar?
>
> jue

[Marshall Dudley]

It appears to not support compression.

Marshall

"Jürgen Exner" wrote:

> Marshall Dudley wrote:

> > When exec is used to shell tar, and tar is piped back to stdout, after
> > the apache timeout, if the download is cancelled, tar locks up and
> > uses 100% of the free cpu time.
> >
> > I have posted the problem in several forums, but cannot get any ideas
> > on it. At this point I don't know if this is an Apache problem,
> > FreeBSD core problem, gtar problem or perl problem.
> >
> > Code line is:
> >
> > exec("/usr/bin/tar cflz - $store_path
> > /home/kingcart/html/store/$username");
> >
> > Anyone have any ideas on at least program/system I should be working
> > on to try and resolve this?

>
> Have you tried using Archive::Tar instead of shelling out to /usr/bin/tar?
>
> jue

[Tim Hammerquist]

Marshall Dudley graced us by uttering:

> "Jürgen Exner" wrote:

> > Marshall Dudley wrote:

> > > When exec is used to shell tar, and tar is piped back to
> > > stdout, [...] Anyone have any ideas on at least
> > > program/system I should be working on to try and resolve
> > > this?

> >
> > Have you tried using Archive::Tar instead of shelling out to
> > /usr/bin/tar?

>
> It appears to not support compression.

tar(1) itself doesn't support compression either.

HOWEVER:

I found the following in `perldoc Archive::Tar`, which you no
doubt looked at:

| If you have the Compress::Zlib module installed, Archive::Tar
| will also support compressed or gzipped tar files.

So, install Archive::Tar, install Compress::Zlib, and then
re-read the Archive::Tar docs, especially the part about the
write() method's second argument...

Cheers,
Tim Hammerquist
--
In 1968 it took the computing power of 2 C-64's to fly a rocket to the moon.
Now, in 1998 it takes the Power of a Pentium 200 to run Microsoft Windows 98.
Something must have gone wrong.