[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Problem with KFM on multiple machines
From:       David Faure <david.faure () insa-lyon ! fr>
Date:       1999-06-02 8:52:55
[Download RAW message or body]

On Wed, Jun 02, 1999 at 10:40:12AM +0200, Matthias Hoelzer-Kluepfel wrote:
> Hi,
> 
> I just commited a fix to the KDE_1_1_BRANCH that deals with
> KFM deadlocks if you run KDE from several machines with NFS
> mounted homes.
> 
> The problem:
> 
> KFM generates a lock file like
> 
> .kde/share/apps/kfm/pid$DISPLAY
> 
> This works well if you start KDE with startx, but it fails if
> you run KDE via KDM, as KDM will set the $DISPLAY var to ":0"
> for the local display. I fixed it with explicitely prepending
> the local host name.
> 
> There are several places in KDEBASE where a function
> "displayName()" is used. For 1.1.2, I fixed them all. For 2.0,
> I think this function should go to the libs. My only question:
> 
> Where should I put this function? 

I'm not sure it's necessary for 2.0 - at least konqueror doesn't
use this at all, since good old socket files have been replaced by Corba,
(and konqy doesn't need a PID file).
But the question remains if other apps need it. Don't know.
Ah yes, lots of apps probably use PID files, to know if they are already
running. Well, I would suggest KApplication::displayName()
(static or not)
-- 
David FAURE
david.faure@insa-lyon.fr, faure@kde.org
http://www.insa-lyon.fr/People/AEDI/dfaure/index.html 
KDE, Making The Future of Computing Available Today

[prev in list] [next in list] [prev in thread] [next in thread]