1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
<html>
<head>
<title>
ht://Dig: htload
</title>
</head>
<body bgcolor="#eef7ff">
<h1>
htload
</h1>
<p>
ht://Dig Copyright © 1995-2001 <a href="THANKS.html">The ht://Dig Group</a><br>
Please see the file <a href="COPYING">COPYING</a> for
license information.
</p>
<hr size="4" noshade>
<dl>
<dd>
<h2>
Synopsis
</h2>
</dd>
<dd>
htload [<em>options</em>]
</dd>
</dl>
<dl>
<dd>
<h2>
Description
</h2>
</dd>
<dd>
Htload reads in an ASCII-text version of the document
database in the same form as the -t option of htdig
and htdump. Note that this will overwrite data in your
databases, so this should be used with great care.
</dd>
</dl>
<dl>
<dd>
<h2>
Options
</h2>
</dd>
<dd>
<dl compact>
<dt>
-a
</dt>
<dd>
Use alternate work files. Tells htload to append <em>
.work</em> to database files, allowing it to
operate on a second set of databases.
</dd>
<dt>
-c <em>configfile</em>
</dt>
<dd>
Use the specified <em>configfile</em> file instead of the
default.
</dd>
<dt>
-i
</dt>
<dd>
Initial. Do not use any old databases. This is
accomplished by first erasing the databases.
</dd>
<dt>
-v
</dt>
<dd>
Verbose mode. This doesn't have much effect.
</dd>
</dl>
</dd>
</dl>
<dl>
<dd>
<h2>
File Formats
</h2>
</dd>
<dl>
<dt>
<h3>Document Database</h3>
</dt>
<dd>
<p>Each line in the file starts with the document id
followed by a list of
<strong><em>fieldname</em>:<em>value</em></strong>
separated by tabs. The fields always appear in the
order listed below:
</p>
<table border=0>
<tr> <th>fieldname</th> <th align="left">value</th></tr>
<tr> <td>u</td><td>URL</td></tr>
<tr> <td>t</td><td>Title</td></tr>
<tr> <td>a</td><td>State (0 = normal, 1 = not found, 2
= not indexed, 3 = obsolete)</td></tr>
<tr> <td>m</td><td>Last modification time as reported
by the server</td></tr>
<tr> <td>s</td><td>Size in bytes</td></tr>
<tr> <td>H</td><td>Excerpt</td></tr>
<tr> <td>h</td><td>Meta description</td></tr>
<tr> <td>l</td><td>Time of last retrieval</td></tr>
<tr> <td>L</td><td>Count of the links in the document
(outgoing links)</td></tr>
<tr> <td>b</td><td>Count of the links to the document
(incoming links or backlinks)</td></tr>
<tr> <td>c</td><td>HopCount of this document</td></tr>
<tr> <td>g</td><td>Signature of the document used for
duplicate-detection</td></tr>
<tr> <td>e</td><td>E-mail address to use for a
notification message from htnotify</td></tr>
<tr> <td>n</td><td>Date to send out a notification
e-mail message</td></tr>
<tr> <td>S</td><td>Subject for a notification e-mail
message</td></tr>
<tr> <td>d</td><td>The text of links pointing to this
document. (e.g. <a
href="docURL">description</a>)</td></tr>
<tr> <td>A</td><td>Anchors in the document (i.e. <A
NAME=...)</td></tr>
</table>
</dd>
<dt>
<h3>Word Database</h3>
</dt>
<dd>
<p>While htdump and htload don't deal with the word database
directly, it's worth mentioning it here because you need to
deal with it when copying the ASCII databases from one system
to another. The initial word database produced by htdig is
already in ASCII format, and a binary version of it is
produced by htmerge, for use by htsearch. So, when you copy
over the ASCII version of the document database produced by
htdump, you need to copy over the wordlist as well, then
run htload to make the binary document database on the target
system, followed by running htmerge to make the word index.
</p>
<p>Each line in the word list file starts with the word
followed by a list of
<strong><em>fieldname</em>:<em>value</em></strong>
separated by tabs. The fields always appear in the
order listed below, with the last two being optional:
</p>
<table border=0>
<tr> <th>fieldname</th> <th align="left">value</th></tr>
<tr> <td>i</td><td>Document ID</td></tr>
<tr> <td>l</td><td>Location of word in document (1 to 1000)</td></tr>
<tr> <td>w</td><td>Weight of word based on scoring factors</td></tr>
<tr> <td>c</td><td>Count of word's appearances in document, if more than 1</td></tr>
<tr> <td>a</td><td>Anchor number if word occurred after a named anchor</td></tr>
</table>
</dd>
</dl>
</dl>
<dl>
<dd>
<h2>
Files
</h2>
</dd>
<dd>
<dl>
<dt>
CONFIG_DIR/htdig.conf
</dt>
<dd>
The default configuration file.
</dd>
<dt>
DATABASE_DIR/db.docs
</dt>
<dd>
The default ASCII document database file.
</dd>
<dt>
DATABASE_DIR/db.wordlist
</dt>
<dd>
The default ASCII word database file.
</dd>
</dl>
</dd>
</dl>
<dl>
<dd>
<h2>
See Also
</h2>
</dd>
<dd>
<a href="htdig.html">htdig</a>,
<a href="htmerge.html">htmerge</a>,
<a href="htdump.html">htdump</a> and
<a href="attrs.html">Configuration file format</a>
</dd>
</dl>
<hr size="4" noshade>
Last modified: $Date: 2001/10/15 02:20:24 $
</body>
</html>
|
