[Kolab-devel] [issue1417] KDE shutdown leading to corrupted index files? Longer shutdown time.

Bernhard Reiter kolab-issues at intevation.de
Mon Sep 18 12:47:36 CEST 2006


New submission from Bernhard Reiter <bernhard at intevation.de>:

Proko2.1.2 on Debian ia32:   
   
Some users just shutdown KDE and the machine at the end of the workday,  
the pattern is observed that there are many corrupt index files.  
Users use periodical syncs.  
The hypothesis is that the shutdown will lead to a kill of kontact,  
raising the change of index file corruption, especially if the sync  
is in process.  
  
Q1: Does this hypothesis has a good chance? Can a kill happen during machine 
shutdown over the KDE menu? 
Q2: If Q1 is yes: Is there a way to raise the delay between SIGTERM and 
SIGKILL? Or is it possible to wait for Kontact to finish?

----------
assignedto: till
messages: 8468
nosy: bernhard, pradeepto, till
priority: urgent
status: unread
title: KDE shutdown leading to corrupted index files? Longer shutdown time.
topic: kde client, kkc
________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://intevation.de/roundup/kolab/issue1417>
________________________________________________




More information about the devel mailing list