Normally a walk is initiated from the administrative interface. There may,
however, be times when it is desirable to start a walk by hand from a
shell (or command) prompt or as
a part of some other automated task. When the administrative interface
starts a walk it shows you the command line to use (using gw
is
discussed later in this section). It is of the form
texis profile=PROFILENAME dowalk/dispatch.txt
You may also specify the parameter ttyverbose
to be 1, or higher,
to tell dowalk to print various status messages to the screen when
being run by hand. The form would be
texis profile=PROFILENAME ttyverbose=1 dowalk/dispatch.txt
Where PROFILENAME
is the name of the profile you have configured
using the administrative interface.
You will need to supply the full path to texis if it is not in your PATH.
You will also need to supply the path to the dowalk script if it is not
in the current directory when you run the command.
INSTALLDIR/bin/texis profile=PROFILENAME
DOCUMENTROOT/webinator/dowalk/dispatch.txt
or
INSTALLDIR\texis profile=PROFILENAME
DOCUMENTROOT/webinator/dowalk/dispatch.txt
Where DOCUMENTROOT is the web document root that you specified during installation.
The walker will behave the same as it does from the administrative interface. Walk info will be logged to the same files. See section 6.1.
There are several other "entry points" that can be used to get
various different behaviors when starting the walker. They all take
the same form as dispatch
above except that dispatch
is replaced by the name of the entry point. The entry points are:
dispatch
stop
ifmodified
Watch URL
. If the watched page has changed a walk
is started. If not no action is taken. This is generally used on a
frequent schedule to automatically rewalk a site if it changes.singles
Single Page
, Page File
, or Page URL
.refresh
recat
Categories
.reindex
Word Definition
expressions.remakeindex
convert
convert
has a different syntax than the others.
texis v2db=DB v2profile=PROFILE v4profile=PROFILE
dowalk/convert.txt
It is used to convert Webinator 2 profiles to Webinator 4 profiles (as well
as possible). Set v2db
to the full path to the existing Webinator
2 database containing the profile to convert. Set v2profile
to the
name of the Webinator 2 profile in the specified database to convert. Set
v4profile
to the name of the new Webinator 4 profile to create in
the global database.
A walk is NOT started. After conversion you would select the new profile, make any adjustments or fixups, then start a new walk.