Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   31559 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

MAKEDBZ(8)					       MAKEDBZ(8)

NAME
       makedbz - rebuild dbz files

SYNOPSIS
       makedbz [ -f filename ] [ -i ] [ -o ] [ -s size ]

DESCRIPTION
       Makedbz rebuilds dbz(3) database.  The default name of the
       text file is <pathdb in inn.conf>/history;  to  specify	a
       different name, use the ``-f'' flag.

OPTIONS
       -f     If the ``-f'' flag is used, then the database files
	      are named file.dir , file.index and file.hash.   If
	      the  ``-f'' flag is not used, then a temporary link
	      to the name history.n  is	 made  and  the	 database
	      files   are   written  as	 history.n.index  ,  his_
	      tory.n.hash and history.n.dir.

       -i     To ignore the old database  use  the  ``-i''  flag.
	      Using  the ``-o'' or ``-s'' flag implies the ``-i''
	      flag.

       -o     If the ``-o'' flag is used, then the  link  is  not
	      made  and	 any existing history files are overwrit
	      ten.  If the old database exists, makedbz will  use
	      it to determine the size of the new database.

       -s     The  program  will  also ignore any old database if
	      the ``-s'' flag is used to specify the  approximate
	      number  of entries in the new database.  Accurately
	      specifying the size is an	 optimization  that  will
	      create a more efficient database.	 (The size should
	      be the estimated eventual size of the  file,  typi
	      cally the size of the old file.)	For more informa
	      tion, see the discussion of dbzfresh and dbzsize in
	      dbz(3).

HISTORY
       Written	by Katsuhiro Kondou <kondou@nec.co.jp> for Inter
       NetNews.	 This is revision 1.1, dated 1999/08/27.

SEE ALSO
       dbz(3), history(5), inn.conf(5).

						       MAKEDBZ(8)

Vote for polarhome