perl -vThis runs the perl interpreter with the option '-v' which stands for 'version'. It should produce a message reading something like This is perl, version 5....
Copies of all of these four packages are also available from the Perl-modules-directory at the PubCrawler-FTP-site.
- LWP (Library for WWW access in Perl), which is part of the libwww-bundle, freely available at CPAN (check the modules/by-module/LWP-directory for a file called libwww-perl-5.36.tar.gz).
- HTML::Parser, necessary for parsing HTML-commands, also available from CPAN (check the modules/by-module/HTML-directory for a file called HTML-Parser-3.10.tar.gz).
- The former two modules depend on the URI-module to be installed (check the modules/by-module/URI-directory at CPAN for a file called URI-1.08.tar.gz).
- The former modules depend on the MIME::Base64-module to be installed (check the modules/by-module/MIME-directory at CPAN for a file called MIME-Base64-2.11.tar.gz).
perl -MLWP -MHTML::Parser -e 42An error message like Can't locate LWP.pm in @INC... indicates that some of the required modules could not be found. This means that you either have to install PubCrawler with precompiled libraries, install the libraries manually, or use an external command line browser.
Background info:Once the package is downloaded and unpacked the program is ready to use. In certain cases some minor changes might be necessary, which are explained in the README file included in the packages.
For each platform accessible to us we have manually installed the additional Perl modules into a local directory - just like a normal user could do it. This involves creating a makefile, putting together files and sometimes compilation of code. The outcome is dependent on the underlying operating system and architecture (the platform), and also on the installed Perl version. After installing and testing the modules we have bundled the whole thing together as a package for that certain platform.
uname -aThis should provide you with information about the operating system and the architecture of your computer. If it doesn't - ask your system administrator.
which lynxThis will show you the location of the program, if available.
gzip -cd <name_of_the_package> | tar xovf -If a browser (like Netscape) was used for downloading the package might have been extracted already during that process. Executing the command mentioned above would result in an error message like gzip: pubcrawler_???.tgz: not in gzip format, whereas '???' stands for the identification of your package.
tar xovf <name_of_the_package>(unpacking without decompression) should do the job.
gzip -cd <name_of_the_package> | tar xovf -In that case a simple
tar xovf <name_of_the_package>(unpacking without decompression) should do the job.
which perlThis should present the full path which has to be inserted in the first line of your PubCrawler script (preceded by special characters #!).
10 07 * * 1-5 "$HOME/pubcrawler.pl" -c "$HOME/pubcrawler.config"Another option is to specify a PubCrawler working directory. This could be for example "$HOME/PubCrawler". All of the PubCrawler-related files like ouput, log and database will be written into this directory (unless diverted by command line option). It will also attempt to read the configuration file from it. So place your pubcrawler.config into the directory, make sure it is readable:
chmod 644 pubcrawler.configand add the following entry to your cron tab file:
10 07 * * 1-5 "$HOME/pubcrawler.pl" -d "$HOME/"
pubcrawler -checkfollowed by any other options. After a short introduction you have to hit <return> to start the check.
pubcrawler.pl -h
ln -s ~/pubcrawler.config ~/presuming that the configuration file is located in the directory ~/PubCrawler (the tilde - '~' - will be evaluated by the operating system to your home directory).
PubCrawler's Home Page