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

List:       kde-devel
Subject:    More verbose umount error message
From:       Falco Hirschenberger <hirschen () itwm ! fraunhofer ! de>
Date:       2005-01-05 9:45:14
Message-ID: 200501051045.17746.hirschen () itwm ! fraunhofer ! de
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Hi,

I think it's very confusing for a user not to be able to umount a device if 
another process accesses it. The error message says that the umounting is 
blocked by a process, but the PID or the process name is not shown.

I thought of a feature like gathering the PID and the process-cmd with a 
routine like in *fuser -m /dev/device* and raising the process window if it 
is a KDE app. Optionally It should be possible to *force* killing the 
accessing process to make it possible to umount the device in any case if the 
priviliges match without the necessity to switch to konsole.

What do you think?

Greets

 Falco

-- 
Falco Hirschenberger <hirsch@bigfoot.de> <ICQ:66107367>
QOTD:
"Good-bye.  I am leaving because I am bored."
                -- George Saunders' dying words

[Attachment #5 (application/pgp-signature)]

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


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