Bug 31736 - kmail lockfile call wrong
Summary: kmail lockfile call wrong
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kdenetwork
Version: 7.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bernhard Rosenkraenzer
QA Contact: Aaron Brown
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-03-13 22:39 UTC by Paul Gampe
Modified: 2013-01-10 21:33 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2001-03-13 22:39:23 UTC


Attachments (Terms of Use)

Description Paul Gampe 2001-03-13 22:39:19 UTC
[pgampe@bob SOURCES]$ kmail --version
Qt: 2.2.4
KDE: 2.1
KMail: 1.2	

kmail version 1.2 does not use the new -ml/-mu options to lockfile when 
the procmail locking option is selected.  Subsequently data can be lost.  
The following patch fixes this:

diff -ruN kdenetwork-2.1.orig/kmail/kmfolder.cpp 
kdenetwork-2.1/kmail/kmfolder.cpp
--- kdenetwork-2.1.orig/kmail/kmfolder.cpp      Mon Feb 19 01:30:36 2001
+++ kdenetwork-2.1/kmail/kmfolder.cpp   Mon Mar 12 16:48:11 2001
@@ -338,7 +338,7 @@
       break;
 
     case procmail_lockfile:
-      cmd_str = "lockfile " + location() + ".lock";
+      cmd_str = "lockfile -ml";
       rc = system( cmd_str.latin1() );
       if( rc != 0 )
       {
@@ -437,7 +437,7 @@
       break;
 
     case procmail_lockfile:
-      cmd_str = "rm -f " + location() + ".lock";
+      cmd_str = "lockfile -mu";
       rc = system( cmd_str.latin1() );
       if( mIndexStream )
       {

Comment 1 Bernhard Rosenkraenzer 2001-03-16 11:55:23 UTC
Fixed in 2.1-6



Note You need to log in before you can comment on or make changes to this bug.