          WWWOFFLE - World Wide Web Offline Explorer - Version 2.5e
          =========================================================

These are miscellaneous files/scripts that can be used with WWWOFFLE.

Contents:

        Debian Startup (I)
        Debian Startup (II)
        Redhat Startup
        Slackware Startup (or other BSD style system)
        S.u.S.E. Startup
        PPPD Start and Stop
        Post WWWOFFLE Script
        WWWOFFLE Usage monitoring
        ISP Configuration
        Log File PID Search
        KPPP Scripts
        Mark URLs not to be purged

Note: I did not write or check all of these scripts, they were supplied to me by
      the authors named below.


Debian Startup (I)
------------------

Filename:    debian-start-stop1
Contributed: Joerg Wittenberger <Joerg.Wittenberger@inf.tu-dresden.de>

> [The script is] Usually called like the system those belong to, e.g., 'bind',
> 'nfs', 'apache'; `wwwoffle' would be a good choice.
>
> Those script go into the `init.d' directory. It's usually either
> '/etc/init.d' because it comprises the system configuration or under
> '/sbin/init.d', or '/usr/sbin/init.d' because to be exact only
> symlinks within the rc<runlevel>.d are the actual config data.


Debian Startup (II)
-------------------

Filename:    debian-start-stop2
Contributed: Remo Petritoli <petritoli@iol.it>

This is a modified version of the one above with some extra features.


Redhat Startup
--------------

Filename:    redhat-init
Contributed: Gianpaolo Macario <macario@tin.it> [Redhat package maintainer]
             Peter Stamfest <e9125730@student.tuwien.ac.at>

> [Name the file] /etc/rc.d/init.d/wwwoffle.init [and make the links]
> ln -sf ../init.d/wwwoffle.init /etc/rc.d/rc3.d/S95wwwoffle.init
> ln -sf ../init.d/wwwoffle.init /etc/rc.d/rc0.d/K17wwwoffle.init
> ln -sf ../init.d/wwwoffle.init /etc/rc.d/rc1.d/K17wwwoffle.init
> ln -sf ../init.d/wwwoffle.init /etc/rc.d/rc6.d/K17wwwoffle.init


Slackware Startup (or other BSD style system)
---------------------------------------------

Filename:    slackware-rc.local
Contributed: Andrew M. Bishop <amb@gedanken.demon.co.uk> [WWWOFFLE Author]

If you have a Slackware system (or other BSD style system) then you can start
wwwoffled by putting it in the rc.local file.  The slackware-rc.local file
should be appended to the /etc/rc.d/rc.local (or /etc/rc.local) file.

It is not important that the wwwoffled demon is killed when the computer is
shutdown.


S.u.S.E. Startup
----------------

Filename:    suse-start-stop
Contributed: Andreas Kupries <a.kupries@westend.com>

> this is the file and the links I am using to start/stop wwwoffled
> during boot/shutdown of my machine (distribution is `S.u.S.e 4.4.1`).
> 
> rc2.d/K18wwwoffle -> ../wwwoffle
> rc2.d/S18wwwoffle -> ../wwwoffle
> rc3.d/K18wwwoffle -> ../wwwoffle
> rc3.d/S18wwwoffle -> ../wwwoffle


PPPD Start and Stop
-------------------

Filenames:   ppp-ip-up & ppp-ip-down
Contributed: Andrew M. Bishop <amb@gedanken.demon.co.uk> [WWWOFFLE Author]

If you use PPP then there will be scripts that the pppd program will run when
the link is connected and before it is disconnected.  These can be used to set
the wwwoffled demon online and offline automatically and to fetch the pages that
have been requested.

The file ppp-ip-up should be appended to the /etc/ppp/ip-up file and the
ppp-ip-down file should be appended to the /etc/ppp/ip-down file.


Post WWWOFFLE Script
--------------------

Filename:    post-wwwoffle.sh
Contributed: Andrew M. Bishop <amb@gedanken.demon.co.uk> [WWWOFFLE Author]

If this script is run after WWWOFFLE is taken offline it will examine the files
that were downloaded while online and can be used to display them.


WWWOFFLE Usage monitoring
-------------------------

Filename:    audit-usage.pl
Contributed: Andrew M. Bishop <amb@gedanken.demon.co.uk> [WWWOFFLE Author]

This script can be run on the WWWOFFLE logfile created by running WWWOFFLE with
debugging output enabled.  It will report the URLs that were requested, what
mode the wwwoffled program is in, which host the request came from and which
user requested them if AllowedConnectUsers section of the configuration file is
used.

Running wwwoffled as shown below gives a logfile with the information required.

wwwoffled -d 4 >  wwwoffled.log 2>&1    # sh/bash Shells
wwwoffled -d 4 >& wwwoffled.log         # csh/tcsh Shells


ISP Configuration
-----------------

Filename:    wwwoffle-config.pl
Contributed: Christian Zagrodnick <zagy@vodoo.boerde.de>

# With wwwoffle-config you can have different configurations for wwwoffle
# in one single file. 
#
# There are two ways of configuring now: `#//+' and `#//-'
# With #//+ the leading `#' in the NEXT line will be removed.
# With #//- the next line will be preceeded with a `#'


Log File PID Search
-------------------

Filename:    log-pid.pl
Contributed: Andrew M. Bishop <amb@gedanken.demon.co.uk> [WWWOFFLE Author]

A Perl script to parse the WWWOFFLE log file output and find all references to
the specified PID for debugging purposes.

Usage: log-pid.pl <pid> < wwwoffle.log


KPPP Scripts
------------

Filename:    kppp-online, kppp-offline
Contributed: Antonio Larrosa <antlarr@arrakis.es>

> In the "Execute" tab of the account setup, the "Upon connect" application
> should be :
> konsole -e <path>/kppp-online
> and the "Upon disconnect" application should be:
> konsole -e <path>/kppp-offline
> 
> where kppp-online and kppp-offline are the attached scripts
> 
> you could also call "kppp-online" directly, but then it would be executed on the
> background and the user wouldn't see the standard output (while fetching pages) 


Mark URLs not to be purged
--------------------------

Filename:    url2keep
Contributed: Jrg Mensmann <joerg.mensmann@gmx.net>

> Here is a new version of "url2keep" (formally known as
> "permcache-netscape.pl"). It now not only works with Netscape's
> bookmarks but has become more flexible.
> 
> Thanks to Jacques L'helgoualc'h <lhh@free.fr> for improving the script
> so that it now works as a filter. It parses HTML code read from stdin
> and outputs all links found there in a format which can be read by the
> config file. See the comments in script for further documentation.
