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

List:       kde-devel
Subject:    Re: KDE libs (kio_file) holding on to files and directories during
From:       Luke Kenneth Casson Leighton <lkcl () lkcl ! net>
Date:       2004-09-28 19:49:51
Message-ID: 20040928200044.GB8349 () lkcl ! net
[Download RAW message or body]

On Tue, Sep 28, 2004 at 09:55:33AM +0200, Stephan Kulow wrote:
> Am Sunday 26 September 2004 15:29 schrieb Luke Kenneth Casson Leighton:
> > > >which still doesn't make me very happy, because i went to all the
> > > >trouble of putting together some stuff with HAL, KVM, autofs and
> > > >fusexmp
> > > >only to find that damn kio_file.la goes and locks the device manually,
> > > >swinnnnee.
> > > 
> > > kio_file isn't supposed to do that. Can you tell which file it has open 
> > > (/proc or lsof)?
> > 
> > it's /dev/hdc.
> > 
> > thanks.
> But by what process? 

> I tried to reproduce and kio_file didn't leave anything
> open, but kded had it open (most likely as Watcher)

 this is with:

 - latest cvs (well, as of two weeks ago).
 - using KDE_FORK_SLAVES (and also KDE_IS_PRELINKED)
 - by NOT having an entry in /etc/fstab for /dev/hdc.
 - by having an entry in /etc/auto.misc (would do the trick)

 these last two are very important because if you have the entry
 in /etc/fstab it gets mounted and you can't press the button on
 the front _anyway_.

-- 
--
Truth, honesty and respect are rare commodities that all spring from
the same well: Love.  If you love yourself and everyone and everything
around you, funnily and coincidentally enough, life gets a lot better.
--
<a href="http://lkcl.net">      lkcl.net      </a> <br />
<a href="mailto:lkcl@lkcl.net"> lkcl@lkcl.net </a> <br />

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]