Skip site navigation (1)Skip section navigation (2)

FreeBSD Manual Pages

  
 
  

home | help
DIDUMP(8)		    System Manager's Manual		     DIDUMP(8)

DILOAD(8)		    System Manager's Manual		     DILOAD(8)

NAME
       didump -	Diablo program to dump the dhistory database

       diload -	Diablo program to append to the	dhistory database

SYNOPSIS
       didump  [ -e ] [	-f ] [ -H ] [ -h ] [ -l	] [ -n ] [ -o ]	[ -p ] [ -rN ]
       [ -TN ] [ -t ] [	-v ] [ -x ] [ -C diablo.config ] [ -d[n] ] [  -V  ]  [
       @offset ] dhistory-file

       diload [	-f ] [ -h hashtablesize	] [ -u ] [ -v ]	[ -C diablo.config ] [
       -d[n] ] [ -V ] [	dhistory-file ]

DESCRIPTION
       Didump dumps the	specified dhistory file	into a human readable  format.
       It is used to debug the dhistory	database, to recover a corrupted dhis-
       tory file.  In combination with diload, didump may be  used  to	remove
       expired entries over rememberdays days old from the dhistory file.

       -e  is  used  to	 cause	didump	to generate ENTRIES lines - useful for
       diload progress.

       -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 ag-
       gregate 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.

       -H Dump a hash trace for	specified Message-ID or	hash.

       -h For each entry dumped, lookup	the hash in the	history	file to	verify
       that it is available via	normal lookup.

       -l is used to force didump to flush each	line to	the output rather then
       buffer  the  output, useful when	running	"didump	-f dhistory | dreadart
       -v -f -"	or something of	that ilk.

       -n Also print the value of the 'next' pointer.

       -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.

       -p Displays progress on stdout. Note that the total records may not  be
       accurate	 if  the -x or -T options are used because didump doesn't know
       how many	records	will be	displayed.

       -rN Set the rememberdays	value to N. The	rememberdays  value  specifies
       the  number  of	days worth of expired articles to keep.	The default is
       obtained	from ``diablo.config'' and a value of '-1' will	 cause	didump
       to  not dump any	expired	articles. If the value has 's',	'm' or 'h' ap-
       pended, the numeric value is taken as seconds, minutes  or  hours,  re-
       spectively. This	option has no effect without the ``-x''	option.

       -TN Don't dump records older than N seconds. The	time value can be suf-
       fixed with 'd', 'h' or 'm' to specify days, hours or minutes.  The  de-
       fault is	'-1' which means dump all records.

       -t  is  used  for  debugging  and causes	didump to attempt to trace the
       dhistory	file's hash table links.  It is	very inefficient.

       -v is used to generate additional information, such as the  spool  file
       containing the article.

       -x causes didump	to not dump expired entries that are over rememberdays
       days old.

       -C allows the specification of the path of the  diablo.config  file  to
       use.

       -d[n] will set debug mode, at optional level n.

       -V will print the version and exit.

       Generally speaking, when	recovering a dhistory file or trimming off ob-
       solete entries, didump or didump	-x is run with	the  existing  history
       file  as	 an  argument,	and the	output is piped	to diload -f tempfile.
       Once the	recovery is complete, the temporary history file is  then  re-
       named  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.

       Diload  takes  history data on the standard input and appends it	to the
       specified history file.	If no history file is  specified,  the	active
       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 diload to append new entries without
       shutting	the main Diablo	server	down,  but  Diablo  must  be  properly
       paused and restarted if you intend to rewrite the history file.

       -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  com-
       pleted.	 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.

       -h hashtablesize	The default hash table size is configured in the  dia-
       blo.config  configuration  file,	 and  is the best way to set the size.
       Alternatively, you can use this option to set it	to any power  of  two.
       For  a  transit	server,	 the  suggested	size is	4m or 8m.  For a spool
       server, the optimal size	is a power of two slightly less	than the  num-
       ber  of	articles  you plan to store (i.e. if you have 90 million arti-
       cles, 64m or perhaps 32m).  Do NOT forget the 'm' for million,  or  you
       will be a very unhappy camper.  Please note that	if you create a	larger
       history hash in this manner, the	next run of diload (perhaps  from  bi-
       weekly.atrim)  will  still only create a	table the size of whatever the
       configured default is, so be sure to modify your	diablo.config  or  bi-
       weekly.atrim to reflect any appropriate changes.

       -u  May be used with special-fast mode to re-enable checking for	dupli-
       cates.  You have	the advantage of locking the history  file  throughout
       the  entire operation, but can still use	a pre-existing history file to
       'update'.

       -v will turn on verbose mode.  diload prints out	its progress.

       -C allows the specification of the path of the  diablo.config  file  to
       use.

       -d[n] will set debug mode, at optional level n.

       -V will print the version and exit.

SEE ALSO
       diablo(8), dicmd(8), didump(8), diload(8), dnewslink(8),	doutq(8), dex-
       pire(8),	 dexpireover(8),  diconvhist(8),  dilookup(8),	 dspoolout(8),
       dnewsfeeds(5), dkp(8), dpath(8),	diablo-kp(5), diablo-files(5)

								     DILOAD(8)

NAME | SYNOPSIS | DESCRIPTION | SEE ALSO

Want to link to this manual page? Use this URL:
<https://www.freebsd.org/cgi/man.cgi?query=didump&sektion=8&manpath=FreeBSD+12.1-RELEASE+and+Ports>

home | help