From 1d7c107c9e9239674b5c7aed32931ab47c50f239 Mon Sep 17 00:00:00 2001 From: Nicolas Williams Date: Mon, 24 Sep 2012 17:48:48 -0500 Subject: Remove MAX_ULOGENTRIES If a master KDC uses only a 64-bit libkadm5srv then there is no reason to impose any limit on ulog size: the practical maximum will be given by the filesystem and available storage space. Even when using a 32-bit libkadm5srv the maximum practical ulog size will be found easily enough when mmap() fails. ticket: 7368 --- src/include/kdb_log.h | 1 - 1 file changed, 1 deletion(-) (limited to 'src/include/kdb_log.h') diff --git a/src/include/kdb_log.h b/src/include/kdb_log.h index beecdc1241..c8d028888a 100644 --- a/src/include/kdb_log.h +++ b/src/include/kdb_log.h @@ -53,7 +53,6 @@ extern "C" { /* * Default ulog file attributes */ -#define MAX_ULOGENTRIES 2500 #define DEF_ULOGENTRIES 1000 #define ULOG_IDLE_TIME 10 /* in seconds */ /* -- cgit