Don't' know if this helps, but....  I am having the same problem with
NewsClipper and the cache.  Since I generate several pages at a time, I
wrote little scripts that then execute as a job (either windoze or *unix,
and just easier for me to edit than individual cron entries).  Well anyway,
I just wrote another simple script that deletes the cache before it then
generates pages.  This ensures that I never have a cache problem....

Be careful though, it can cause you to be much more stressful on the remote
sites!

-jbg

-----------------------
James B. Goodman
[EMAIL PROTECTED]
310.989.9226 (voice)
310.458.3136 (fax)
http://www.recordstore.com

-----Original Message-----
From: Jeff Lessem [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 21, 2000 4:30 PM
To: David Coppit
Cc: News Clipper Mailing List
Subject: Re: File::Cache undefined value bug

In your message of: Mon, 21 Aug 2000 16:53:48 EDT, you write:
>
>Howdy:
>
>As I mentioned before, the undefined value bug is a problem in the
>File::Cache module that News Clipper uses. I've submitted a patch, and
>am waiting for the new release of the module.
>
>In the meantime, people experiencing the File::Cache undefined value
>problem can do the following to fix it. (This only applies to users
>that are not running the pre-compiled versions.)

This almost works for me.  I no longer have trouble with the
File::Cache undefined value bug, but I now get a memory fault.

I have changed the appropriate parts of Cache.pm to read:

        #   %$data_ref = %{ thaw($frozen_object_data) };
        # Start Patch
        #    if the %$frozen_object_data is corrupted, thaw will return
undef
            my $thawed_data = thaw($frozen_object_data);

            return unless defined $thawed_data;

            %$data_ref = %$thawed_data;
        # End Patch

Running NewsClipper -d shows that the cache is located in
/home/lessem/.NewsClipper/cache, which is correct, and maxcachesize is
10485760, which is also correct.  With an empty cache NewsClipper will
run, but once the cache is populated it will usually die on the first
URL it checks, but occasionally it will get past the first one.  For
each one it gives something like:

<!--DEBUG: GetUrl is getting
     -->
<!--DEBUG:
weather.com/weather/us/zips/80303.html              -->
<!--DEBUG: Checking cache for data for
     -->
<!--DEBUG:
weather.com/weather/us/zips/80303.html              -->
<!--DEBUG: Couldn't find cached
     -->

and the run abruptly ends with:
bin/NewsClipper.sh: 16434 Memory fault
(the address changes, NewsClipper.sh is
    #!/bin/sh
    #rm -rf /home/lessem/.NewsClipper/cache
    /usr/local/bin/NewsClipper.pl $@ -i
/home/lessem/public_html/template.txt \
    -o /home/lessem/public_html/NewsClipper.html
)

I can find the appropriate page in the cache, so I don't know why
NewsClipper can't.  All of the pages in my cache contain a bit of
binary data at the beginning and end.  I assume this is put there by
the cache.

If there is any other debugging information I can provide, please let
me know.  I am using perl v5.6.0 built for alpha-dec_osf and
NewsClipper 1.24 Open Source.

--
Jeff Lessem.

-
If you would like to unsubscribe from this mailing list send an email to
[EMAIL PROTECTED] with the body "unsubscribe newsclipperlist
YOUR_EMAIL_ADDRESS" (without the quotes) or use the form provided at
http://www.NewsClipper.com/TechSup.htm#MailingList.


-
If you would like to unsubscribe from this mailing list send an email to 
[EMAIL PROTECTED] with the body "unsubscribe newsclipperlist 
YOUR_EMAIL_ADDRESS" (without the quotes) or use the form provided at 
http://www.NewsClipper.com/TechSup.htm#MailingList.

Reply via email to