From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id D4B821384C4 for ; Tue, 15 Jan 2013 22:56:22 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id BE69221C0A0; Tue, 15 Jan 2013 22:56:11 +0000 (UTC) Received: from mail-gh0-f178.google.com (mail-gh0-f178.google.com [209.85.160.178]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 2478D21C07C for ; Tue, 15 Jan 2013 22:56:09 +0000 (UTC) Received: by mail-gh0-f178.google.com with SMTP id g24so71257ghb.9 for ; Tue, 15 Jan 2013 14:56:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:x-enigmail-version:content-type; bh=/tAWhol695OK8ZiQ0mno7cpmQLTisL28wnH+UQu4+Yk=; b=RANQ7c/cWzf0bhyKAEHDGiVDW8BDE31sO9hiI/g/NNUDhQ1f/zTl/MBhB1puqakBKY 1GsuI/rLfDluXHNkItrdrcS0/mvqT7qD8QU5/myTfhJHcBGCRUAZXzk4OzpjJpUUZ526 O0TMcv7YmrTxjw6QsVyPNQw5pxr0PmCDVj+cYe//4pql50rAIfz02wcXC26l2f+91Ni6 /+sKgM2/5DYu18urHrVG1aW5CNxaLzHvmiBuhcKsDQp7zCwOBSQuQkQx7guF+BQpTLMU pafoa+ltcZcTSqonDWpYHBCFK4TjC+TuoKSfIYrSWeG4fDn3iyZjQ8HhonATLWOijEu5 5apg== X-Received: by 10.100.211.4 with SMTP id j4mr20066996ang.67.1358290569279; Tue, 15 Jan 2013 14:56:09 -0800 (PST) Received: from [192.168.2.5] (adsl-65-0-118-184.jan.bellsouth.net. [65.0.118.184]) by mx.google.com with ESMTPS id e39sm15365416ani.16.2013.01.15.14.56.07 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 15 Jan 2013 14:56:08 -0800 (PST) Message-ID: <50F5DE86.2000105@gmail.com> Date: Tue, 15 Jan 2013 16:56:06 -0600 From: Dale User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 SeaMonkey/2.15 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: /home doesn't umount on shutdown References: <20130115115721.16ea5ca0@khamul.example.com> <20130115110956.5c7e5a17@digimed.co.uk> <20130115145826.00706056@khamul.example.com> In-Reply-To: X-Enigmail-Version: 1.5 Content-Type: multipart/alternative; boundary="------------080809090208000104090109" X-Archives-Salt: 56daf73a-7926-4369-aa08-fb93dcca6a74 X-Archives-Hash: 0790882d873146109616dbe85949cc9f This is a multi-part message in MIME format. --------------080809090208000104090109 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Remy Blank wrote: > Alan McKinnon wrote: >> But I was not able to make the problem re-appear in short reboot >> cycles. So whatever is hanging the box is something that starts up in >> the course of work, it doesn't appear to be there directly after a KDE >> login. > > I have observed that kded4 and nepomukserver sometimes don't terminate > after logging out of KDE. At the next login, I get another copy of each, > and so they accumulate. It's so bad that I added a script to > ~/.kde4/shutdown to "kill -9" them if they are still running 15 seconds > after logging out. > > Both processes keep open file descriptors to ~/.xsession-errors, so they > would indeed prevent /home from unmounting. > > -- Remy > I run into that a LOT here too. After a large upgrade, I usually switch to the boot runlevel to make sure most everything gets reloaded. When I do that, I have to kill some leftover kde stuff manually. I have been known to let it sit for several minutes to see if it will eventually kill itself but it never has. The nepomukserver is one of them but there is another one that I can't recall the name of. May be on to something, hopefully. Care to share that script? ;-) May try that myself. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words! --------------080809090208000104090109 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit Remy Blank wrote:
> Alan McKinnon wrote:
>> But I was not able to make the problem re-appear in short reboot
>> cycles. So whatever is hanging the box is something that starts up in
>> the course of work, it doesn't appear to be there directly after a KDE
>> login.
>
> I have observed that kded4 and nepomukserver sometimes don't terminate
> after logging out of KDE. At the next login, I get another copy of each,
> and so they accumulate. It's so bad that I added a script to
> ~/.kde4/shutdown to "kill -9" them if they are still running 15 seconds
> after logging out.
>
> Both processes keep open file descriptors to ~/.xsession-errors, so they
> would indeed prevent /home from unmounting.
>
> -- Remy
>


I run into that a LOT here too.  After a large upgrade, I usually switch to the boot runlevel to make sure most everything gets reloaded.  When I do that, I have to kill some leftover kde stuff manually.  I have been known to let it sit for several minutes to see if it will eventually kill itself but it never has.  The nepomukserver is one of them but there is another one that I can't recall the name of.

May be on to something, hopefully.

Care to share that script?  ;-)  May try that myself.

Dale

:-)  :-)

--
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!

--------------080809090208000104090109--