From 30be9a32fd26a2d08aa4413942408500c93ad4a3 Mon Sep 17 00:00:00 2001 From: Adam Dickmeiss Date: Sun, 22 Feb 2009 13:10:53 +0100 Subject: [PATCH] Disable YAZ' own log rotate by default (no 1 GB limit). The variable l_max_size which specifies the log file limit is set to 0 (DISABLED): This is due to the fact that YAZ is most often deployed using logrotate. Also YAZ can not perform log rotate because of unsufficient permissions (setuid). --- src/log.c | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/src/log.c b/src/log.c index db9af9e..e58e00e 100644 --- a/src/log.c +++ b/src/log.c @@ -73,11 +73,14 @@ static char l_new_default_format[] = "%Y%m%d-%H%M%S"; static char l_custom_format[TIMEFORMAT_LEN] = ""; static char *l_actual_format = l_old_default_format; -/** l_max_size tells when to rotate the log. Default is 1 GB - This is almost the same as never, but it saves applications in the - case of 2 or 4 GB file size limits.. +/** l_max_size tells when to rotate the log. The default value is + 0 which means DISABLED. This is to be preffered if YAZ runs + as a server using logrotate etc. + A positive size specifies the file size in bytes when a log rotate + will occur. Note that in order for this to work YAZ must have + permissions to do so. */ -static int l_max_size = 1024*1024*1024; +static int l_max_size = 0; #define MAX_MASK_NAMES 35 /* 32 bits plus a few combo names */ static struct { -- 1.7.10.4