[Kolab-devel] [issue4539] consolidation of log files in one place

[Christoph Wickert]

New submission from Christoph Wickert <wickert at kolabsys.com>:

We have way to many log files scattered across the system:

# find /kolab/ -name \*.log | sort
/kolab/var/amavisd/amavisd.log
/kolab/var/apache/log/access.log
/kolab/var/apache/log/apache-access.log
/kolab/var/apache/log/apache-error.log
/kolab/var/apache/log/error.log
/kolab/var/apache/log/php/php-errors.log
/kolab/var/clamav/clamd.log
/kolab/var/clamav/freshclam.log
/kolab/var/fsl/fsl.log
/kolab/var/imapd/log/cyr_db.log
/kolab/var/imapd/log/cyrmaster.log
/kolab/var/imapd/log/imapd.log
/kolab/var/imapd/log/lmtpd.log
/kolab/var/imapd/log/misc.log
/kolab/var/imapd/log/notifyd.log
/kolab/var/imapd/log/pop3d.log
/kolab/var/imapd/log/sieve.log
/kolab/var/kolab-filter/log/filter.log
/kolab/var/kolab-freebusy/log/freebusy.log
/kolab/var/kolab-freebusy/log/php-error.log
/kolab/var/kolab/www/client/log/horde.log
/kolab/var/kolab/www/client/log/php-errors.log
/kolab/var/openldap/openldap.log
/kolab/var/postfix/log/postfix.log
/kolab/var/sasl/log/saslauthd.log
/kolab/var/spamassassin/spamassassin.log
/kolab/var/z-push/log/access.log

We should consolidate everything in one central place. I think /kolab/var/log is
the best place as it is not specific to a component and tries to follow the FHS,
see http://www.pathname.com/fhs/pub/fhs-2.3.html#VARLOGLOGFILESANDDIRECTORIES


Proposal:

/kolab/var/postfix/log/postfix.log -> /kolab/var/log/postfix.log
/kolab/var/spamassassin/spamassassin.log -> /kolab/var/log/spamassassin.log
/kolab/var/kolab-freebusy/log/freebusy.log -> /kolab/var/log/kolab/freebusy.log
or /kolab/var/log/kolab-freebusy.log
/kolab/var/kolab-freebusy/log/php-error.log ->
/kolab/var/log/kolab/freebusy-php-error.log or
/kolab/var/log/kolab-freebusy-php-error.log???
/kolab/var/openldap/openldap.log -> /kolab/var/log/openldap.log
/kolab/var/fsl/fsl.log -> /kolab/var/log/fsl.log
/kolab/var/kolab-filter/log/filter.log -> /kolab/var/log/kolab/filter.log or
/kolab/var/log/kolab-filter.log
/kolab/var/sasl/log/saslauthd.log -> /kolab/var/log/saslauthd.log
/kolab/var/kolab/www/client/log/php-errors.log ->
/kolab/var/log/client/php-errors.log or /kolab/var/log/kolab/client-php-errors.log
/kolab/var/kolab/www/client/log/horde.log -> /kolab/var/log/client/horde.log or
/kolab/var/log/kolab/webclient.log
/kolab/var/z-push/log/access.log -> /kolab/var/log/z-push/access.log
/kolab/var/imapd/log/pop3d.log -> /kolab/var/log/imapd/pop3d.log
/kolab/var/imapd/log/lmtpd.log -> /kolab/var/log/imapd/lmtpd.log
/kolab/var/imapd/log/imapd.log -> /kolab/var/log/imapd/imapd.log
/kolab/var/imapd/log/cyrmaster.log -> /kolab/var/log/imapd/cyrmaster.log
/kolab/var/imapd/log/misc.log -> /kolab/var/log/imapd/misc.log
/kolab/var/imapd/log/notifyd.log -> /kolab/var/log/imapd/notifyd.log
/kolab/var/imapd/log/sieve.log -> /kolab/var/log/imapd/sieve.log
/kolab/var/imapd/log/cyr_db.log -> /kolab/var/log/imapd/cyr_db.log
/kolab/var/apache/log/php/php-errors.log -> /kolab/var/log/apache/php-errors.log
/kolab/var/apache/log/access.log -> /kolab/var/log/apache/access.log
/kolab/var/apache/log/error.log -> /kolab/var/log/apache/error.log
/kolab/var/apache/log/apache-error.log -> /kolab/var/log/apache/apache-error.log
/kolab/var/apache/log/apache-access.log -> /kolab/var/log/apache/access.log
/kolab/var/amavisd/amavisd.log -> /kolab/var/log/amavisd.log
/kolab/var/clamav/freshclam.log -> /kolab/var/log/freshclam.log
/kolab/var/clamav/clamd.log -> /kolab/var/log/clamd.log


Result:

/kolab/var/log/amavisd.log
/kolab/var/log/apache/access.log
/kolab/var/log/apache/access.log
/kolab/var/log/apache/apache-error.log
/kolab/var/log/apache/error.log
/kolab/var/log/apache/php-errors.log
/kolab/var/log/clamd.log
/kolab/var/log/client/horde.log or /kolab/var/log/kolab/webclient.log
/kolab/var/log/client/php-errors.log or /kolab/var/log/kolab/client-php-errors.log
/kolab/var/log/freshclam.log
/kolab/var/log/fsl.log
/kolab/var/log/imapd/cyr_db.log
/kolab/var/log/imapd/cyrmaster.log
/kolab/var/log/imapd/imapd.log
/kolab/var/log/imapd/lmtpd.log
/kolab/var/log/imapd/misc.log
/kolab/var/log/imapd/notifyd.log
/kolab/var/log/imapd/pop3d.log
/kolab/var/log/imapd/sieve.log
/kolab/var/log/kolab/filter.log or /kolab/var/log/kolab-filter.log
/kolab/var/log/kolab/freebusy.log or /kolab/var/log/kolab-freebusy.log
/kolab/var/log/kolab/freebusy-php-error.log or
/kolab/var/log/kolab-freebusy-php-error.log???
/kolab/var/log/openldap.log
/kolab/var/log/postfix.log
/kolab/var/log/saslauthd.log
/kolab/var/log/spamassassin.log
/kolab/var/log/z-push/access.log

General questions:

1. Do we want subfolders for each component or only for the ones that have at
least x logfiles? E.g. for /kolab/var/log/z-push/access.log I proposed the
folder as there can be also a debug.txt.

2. Do we need subfolders due to permissions?

Specific files:

3. As for /kolab/var/imapd/log/misc.log I think it's best to just nuke it. It
hardly holds any information and that information could easily go into 

4. /kolab/var/apache/log/error.log and 
/kolab/var/apache/log/apache-error.log is confusing. Should be combined into a
single file. Same for access.log and apache-access.log

5. What about the 3 php-error.log files we have? Does it make sense to combine
them into two, e.g. one for php errors from the php package and another one for
apache-php, this means apache/php-errors.log and /log/client/php-errors.log?

----------
assignedto: cwickert
keyword: server
messages: 26343
nosy: cwickert, jmeeuwen, thomas, wilde, wrobel
priority: wish
status: unread
title: consolidation of log files in one place

______________________________________
Kolab issue tracker <issues at kolab.org>
<https://issues.kolab.org/issue4539>
______________________________________