[Kolab-devel] [issue4024] Lots of tmp files in kolab's configuration directory

[Richard Bos]

New submission from Richard Bos <ml at radoeka.nl>:

There are really lots of temp files left behind since Mathieu's change to
kolabconf.  For example:

linux-geis:/etc/kolab # ls -ltr tmp*.kolabtmp | wc -l
793

linux-geis:/etc/kolab # ls -ltr tmp*.kolabtmp  | tail -10
-rw------- 1 root root  2979 Jan 12 12:07 tmp2287Y.kolabtmp
-rw------- 1 root root  2408 Jan 12 12:07 tmptNa73.kolabtmp
-rw------- 1 root root   882 Jan 12 12:07 tmpOyqGc.kolabtmp
-rw------- 1 root root  3262 Jan 12 12:07 tmpzoTAh.kolabtmp
-rw------- 1 root root  5634 Jan 12 12:07 tmp91hes.kolabtmp
-rw------- 1 root root  1845 Jan 12 12:07 tmpaZ0qk.kolabtmp
-rw------- 1 root root  1066 Jan 12 12:07 tmpYFp4E.kolabtmp
-rw------- 1 root root    49 Jan 12 12:07 tmpf26jn.kolabtmp
-rw------- 1 root root  6331 Jan 12 12:07 tmpJue3H.kolabtmp
-rw------- 1 root root   696 Jan 12 12:07 tmpG6z4t.kolabtmp


linux-geis:/etc/kolab # cat tmpG6z4t.kolabtmp
##  Copyright (c) 2004 Klaraelvdalens Datakonsult AB
##     Written by Steffen Hansen <steffen at klaralvdalens-datakonsult.se>
##
## This program is Free Software under the GNU General Public License (>=v2).
## Read the file COPYING that comes with this packages for details.

#=================================================================
# THIS FILE IS AUTOMATICALLY WRITTEN BY THE KOLAB CONFIG BACKEND.
# MANUAL CHANGES ARE LOST UNLESS MADE IN THE TEMPLATE FILE:
#
#  /etc/kolab/templates/slapd.replicas.template
#
# Changes can be activated by running /usr/sbin/kolabconf
#=================================================================

# Replica statements for inclusion in slapd.conf


Probably caused by this code in /usr/lib/perl5/vendor_perl/5.10.0/Kolab/Conf.pm:
134     if (!($config = new File::Temp( TEMPLATE => 'tmpXXXXX',
135                                     DIR => $Kolab::config{"kolabdir"},
136                                     SUFFIX => '.kolabtmp',
137                                     UNLINK => 0 ))) {
138         Kolab::log('T', "Unable to open configuration file `$cfg': $!",
KOLAB_ERROR);
139         exit(1);
140     }

It looks like that the files are not removed (automatically).

Why is kolab configuration directory used for this and not /tmp?

----------
keyword: server
messages: 23067
nosy: mathieu.parent, rbos, thomas, wilde, wrobel
priority: bug
status: unread
title: Lots of tmp files in kolab's configuration directory

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