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
|
.\" $Revision: 1.00 $
.TH DIDUMP 8
.TH DILOAD 8
.SH NAME
didump \- Diablo program to dump the dhistory database
.PP
diload \- Diablo program to append to the dhistory database
.SH SYNOPSIS
.B didump
[
.B \-f
]
[
.B \-x
]
[
.B \-t
]
.B dhistory-file
.PP
.B diload
[
.B \-v
]
[
.B \-f
]
[
.B \-h hashtablesize
]
[
.B \-u
]
[
.B \-o
]
[
.B dhistory-file
]
.SH DESCRIPTION
.IR Didump
dumps the specified dhistory file into a human readable format. It is
used to debug the dhistory database, to recover a corrupted dhistory
file. In combination with diload, didump may be used to remove expired
entries over 16 days old from the dhistory file.
.PP
.B -x
causes didump to not dump expired entries that are over 16 days old.
.PP
.B -t
is used for debugging and causes didump to attempt to trace the dhistory
file's hash table links. It is very inefficient.
.PP
.B -o
DiDump V1.08 can read older (V1.07 or smaller) Diablo dhistory files if this
option is specified. This is used when upgrading to 1.08 to reload the
dhistory file with the dhistory file format.
.PP
.B -f
with a normal dump (no -t), seeks to the end of the history file and
prints out entries as other programs (diablo) add them. DiDump will
not exit in this case. This option is useful to get an idea of the
aggregate incoming article rate. NOTE, however, that diablo does not
add history file entries with a simple append, so you may see blank records
in the output that, in fact, are filled-in later.
.PP
.B -h hashtablesize
The default hash table size is 4 million entries (-h 4m). You can set it to
any power of two but the suggested size is 4m or 8m. Do NOT forget the 'm'
for million, or you will be a very unhappy camper.
.PP
Generally speaking, when recovering a dhistory file or trimming off
obsolete entries,
.B didump
or
.B didump -x
is run with the existing history file as an argument, and the output is
piped to
.IR diload
\-f tempfile.
Once the recovery is complete, the temporary history file is then renamed
to become the actual history file. The diablo server must be paused
during such operations to prevent it from acting on the 'old' version
of the history file while the new one is being constructed.
.PP
.IR Diload
takes history data on the standard input and appends it to the
specified history file. If no history file is specified, the
active
.B dhistory
database is used. If any given record already exists in the dhistory file,
the new record is thrown away and the original record left intact. You can
safely run
.IR diload
to append new entries without shutting the main Diablo server down, but
Diablo must be shutdown if you intend to rewrite the history file.
.PP
.B -v
Turn on verbose mode. diload prints out its progress.
.PP
.B -f
Turn on special-fast mode. This locks the history file through the
entire procedure and makes the assumption that entries being added
did not previously exist. This also causes the base hash table to
be cached and written then written out when the load operation has
completed. DiLoad will create the history file you supply as an argument
and will refuse to run if it is already pre-existing. This
is used in the weekly trimming script to quickly rebuild the history
file from a dump.
.PP
.B -u
May be used with special-fast mode to re-enable checking for duplicates.
You have the advantage of locking the history file throughout the
entire operation, but can still use a pre-existing history file to 'update'.
.SH "SEE ALSO"
diablo(8),
dclean(8),
dicmd(8),
didump(8),
diload(8),
dnewslink(8),
doutq(8),
dexpire(8)
diconvhist(8),
dilookup(8),
dspoolout(8),
dnewsfeeds(5),
dkp(8),
diablo-kp(5),
diablo-files(5)
.PP
|
