From 8b4acb9ed53e19c469ef496af2e7d7be5517c44c Mon Sep 17 00:00:00 2001 From: Keith Bostic Date: Sun, 8 Sep 1991 18:24:45 -0800 Subject: [PATCH] comment out maxkeypage for now SCCS-vsn: lib/libc/db/man/btree.3 5.2 --- usr/src/lib/libc/db/man/btree.3 | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/usr/src/lib/libc/db/man/btree.3 b/usr/src/lib/libc/db/man/btree.3 index 0b07fe8a1e..bbd243f245 100644 --- a/usr/src/lib/libc/db/man/btree.3 +++ b/usr/src/lib/libc/db/man/btree.3 @@ -3,7 +3,7 @@ .\" .\" %sccs.include.redist.man% .\" -.\" @(#)btree.3 5.1 (Berkeley) %G% +.\" @(#)btree.3 5.2 (Berkeley) %G% .\" .TH BTREE 3 "" .UC 7 @@ -41,8 +41,8 @@ u_int cachesize; index_t psize; .br int lorder; -.br -int maxkeypage; +.\" .br +.\" int maxkeypage; .br int minkeypage; .br @@ -100,16 +100,16 @@ big endian order would be the number 4,321. If .I lorder is 0 (no order is specified) the current host order is used. -.TP -maxkeypage -The maximum number of keys which will be stored on any single page. -Because of the way the btree data structure works, -.I maxkeypage -must always be greater than or equal to 2. -If -.I maxkeypage -is 0 (no maximum number of keys is specified) the page fill factor is -made as large as possible (which is almost invariably what is wanted). +.\" .TP +.\" maxkeypage +.\" The maximum number of keys which will be stored on any single page. +.\" Because of the way the btree data structure works, +.\" .I maxkeypage +.\" must always be greater than or equal to 2. +.\" If +.\" .I maxkeypage +.\" is 0 (no maximum number of keys is specified) the page fill factor is +.\" made as large as possible (which is almost invariably what is wanted). .TP minkeypage The minimum number of keys which will be stored on any single page. -- 2.20.1