Kolab 3.4 on CentOS 32bit 6.7 (path confg for /dev/shm)

Soliva Andrea soliva at comcept.ch
Tue Aug 25 09:43:40 CEST 2015


Hi all

I tried for testing purpose and for performance reason to define path in 
/etc/imapd.conf to move some files/dir to /dev/shm (tmpfs):

         # vi /etc/impad.conf

         --------------- /etc/impad.conf ---------------

         configdirectory: /var/lib/imap
         # $confdir/proc/ will be used if not defined "proc_path"
         proc_path: /dev/shm
         # $confdir/lock will be used if not defined "mboxname_lockpath"
         mboxname_lockpath: /dev/shm
         # $confdir/statuscache.db will be used if not defined 
"statuscache_db_path"
         statuscache_db_path: /dev/shm/statuscache.db
         # $confdir/tls_sessions.db will be used if not defined 
"tls_sessions_db_path"
         tls_sessions_db_path: /dev/shm/tls_sessions.db
         # $confdir/deliver.db will be used if not defined 
"duplicate_db_path"
         duplicate_db_path: /dev/shm/deliver.db

         --------------- /etc/impad.conf ---------------

On regular base this works out of the box but as soon as I try to delete 
a user some ERRORS are shown:

Aug 24 08:50:25 kolab imap/imaps[7782]: Deleted mailbox 
comcept.ch!user.andrea^soliva
Aug 24 08:50:25 kolab imap/imaps[7782]: IOERROR: bogus filename 
"/dev/shm//tls_sessions.db" in proc_foreach
Aug 24 08:50:25 kolab imap/imaps[7782]: IOERROR: bogus filename 
"/dev/shm//deliver.db" in proc_foreach
Aug 24 08:50:25 kolab imap/imaps[7782]: IOERROR: bogus filename 
"/dev/shm//sem.slapd-kolab.stats" in proc_foreach
Aug 24 08:50:25 kolab imap/imaps[7782]: IOERROR: bogus filename 
"/dev/shm//q" in proc_foreach
Aug 24 08:50:25 kolab imap/imaps[7782]: IOERROR: bogus filename 
"/dev/shm//n" in proc_foreach
Aug 24 08:50:25 kolab imap/imaps[7782]: IOERROR: bogus filename 
"/dev/shm//statuscache.db" in proc_foreach
Aug 24 08:50:25 kolab imap/imaps[7782]: IOERROR: bogus filename 
"/dev/shm//domain" in proc_foreach

The issue here seems to me the "/dev/shm//" dir Definition with two 
"//". If I define for "proc" "lock" as "statuscache_db" links to 
/dev/shm it works but not for "tls_session_db" which means if a new db 
is created even the link exists it is done in /var/lib/imap/. Did 
anybody also try this path's etc. Is my defintion in /etc/imapd.conf not 
right?

Anybody any comment?

-- 
Kind regards
-- 
Mit freundlichen Grüssen

Andrea Soliva

Email: andrea.soliva at comcept.ch



Andrea Soliva

Email: andrea.soliva at comcept.ch


More information about the users mailing list