From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-user+bounces-171681-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
	by finch.gentoo.org (Postfix) with ESMTP id 7C0B913829C
	for <garchives@archives.gentoo.org>; Fri, 10 Jun 2016 19:55:04 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 423F914209;
	Fri, 10 Jun 2016 19:54:51 +0000 (UTC)
Received: from gw2.antarean.org (gw2.antarean.org [141.105.125.208])
	by pigeon.gentoo.org (Postfix) with ESMTP id 00D1F21C038
	for <gentoo-user@lists.gentoo.org>; Fri, 10 Jun 2016 19:54:49 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
	by gw2.antarean.org (Postfix) with ESMTP id 3B99D121EFB
	for <gentoo-user@lists.gentoo.org>; Fri, 10 Jun 2016 19:53:45 +0000 ()
X-Virus-Scanned: amavisd-new at antarean.org
Received: from gw2.antarean.org ([127.0.0.1])
	by localhost (gw2.antarean.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id RDkRyeLxnrZn for <gentoo-user@lists.gentoo.org>;
	Fri, 10 Jun 2016 19:53:43 +0000 (%Z)
Received: from data.antarean.org (localhost [127.0.0.1])
	by gw2.antarean.org (Postfix) with ESMTP id C8C4012175E
	for <gentoo-user@lists.gentoo.org>; Fri, 10 Jun 2016 19:53:43 +0000 ()
Received: from nl019.gst.antarean.org (nl019.gst.antarean.org [192.168.45.119])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by data.antarean.org (Postfix) with ESMTPSA id 881784C
	for <gentoo-user@lists.gentoo.org>; Fri, 10 Jun 2016 21:54:06 +0200 (CEST)
In-Reply-To: <4686288.0tEWZtr5JR@dell_xps>
References: <7081971.LXnDv28ARm@dell_xps> <8598600.aLmdYVC2JS@dell_xps> <1527707.PoHdVoyLOS@andromeda> <4686288.0tEWZtr5JR@dell_xps>
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain;
 charset=UTF-8
Subject: Re: [gentoo-user] Recommended way to shut down akonadi
From: "J. Roeleveld" <joost@antarean.org>
Date: Fri, 10 Jun 2016 19:54:44 +0000
To: gentoo-user@lists.gentoo.org
Message-ID: <9327B687-2B70-4DB0-BB83-A5D6D9E66773@antarean.org>
X-Archives-Salt: 97100ce7-30d2-4a5c-ab4f-14f49fef795d
X-Archives-Hash: 3833ee16a402052f97cb979ef573a379

On June 10, 2016 6:05:56 PM GMT+02:00, Mick <michaelkintzios@gmail.com> wrote:
>On Tuesday 07 Jun 2016 10:13:12 J. Roeleveld wrote:
>
>> On Monday, June 06, 2016 07:22:09 PM Mick wrote:
>> > I do not have KDEPIM systray enabled and I shutdown Kmail before I
>> > shutdown
>> > the PC.
>> > 
>> > These are the relevant processes I see:
>> > 
>> > 29961 ? SNl 0:09 kmail -caption KMail
>> > 29968 ? SNl 0:00 /usr/bin/akonadi_control
>> > 29970 ? SNl 0:08 \_ akonadiserver
>> > 29998 ? SNl 0:00 \_ /usr/bin/akonadi_agent_launcher
>> > akonadi_akonotes_resource akonadi_akonotes_resource_0
>> > 29999 ? SN 0:00 \_ /usr/bin/akonadi_archivemail_agent
>> > --identifier akonadi_archivemail_agent
>> > 30000 ? SN 0:02 \_ /usr/bin/akonadi_baloo_indexer --identifier
>> > akonadi_baloo_indexer
>> > 30001 ? SNl 0:00 \_ /usr/bin/akonadi_agent_launcher
>> > akonadi_contacts_resource akonadi_contacts_resource_1
>> > 30002 ? SN 0:00 \_ /usr/bin/akonadi_followupreminder_agent --
>> > identifier akonadi_followupreminder_agent
>> > 30007 ? SNl 0:00 \_ /usr/bin/akonadi_imap_resource --identifier
>> > akonadi_imap_resource_0
>> > 30008 ? SNl 0:02 \_ /usr/bin/akonadi_imap_resource --identifier
>> > akonadi_imap_resource_1
>> > 30009 ? SNl 0:00 \_ /usr/bin/akonadi_agent_launcher
>> > akonadi_maildir_resource akonadi_maildir_resource_0
>> > 30010 ? SN 0:00 \_ /usr/bin/akonadi_maildispatcher_agent --
>> > identifier akonadi_maildispatcher_agent
>> > 30013 ? SN 0:00 \_ /usr/bin/akonadi_mailfilter_agent
>> > --identifier akonadi_mailfilter_agent
>> > 30014 ? SN 0:00 \_ /usr/bin/akonadi_migration_agent --identifier
>> > akonadi_migration_agent
>> > 30015 ? SN 0:00 \_ /usr/bin/akonadi_newmailnotifier_agent --
>> > identifier akonadi_newmailnotifier_agent
>> > 30016 ? SN 0:00 \_ /usr/bin/akonadi_sendlater_agent --identifier
>> > akonadi_sendlater_agent
>> > 30023 ? SNl 0:00 \_ /usr/bin/akonadi_agent_launcher
>> > akonadi_vcard_resource akonadi_vcard_resource_1
>> > 30024 ? SNl 0:00 \_ /usr/bin/akonadi_agent_launcher
>> > akonadi_vcard_resource akonadi_vcard_resource_2
>> > 29974 ? SNs 0:00 kdeinit4: kdeinit4 Runnin e
>> > 29976 ? SN 0:00 \_ kdeinit4: klauncher [kdei e
>> > 29979 ? SN 0:00 kdeinit4: kded4 [kdeinit]
>> > 29997 ? SNL 0:00 kdeinit4: kwalletd [kdein e
>> > 30101 ? SNl 0:00 /usr/bin/knotify4
>> > 
>> > after I login and start Kmail.
>> > 
>> > I did try 'killall kdeinit4' but from what I recall it made no
>difference.
>> > Happy to try any suggestions/syntax you may have.
>> 
>> Not able to test as I use KDE.
>> But, you could try:
>> # killall akonadi_control
>> or
>> # akonadictl stop
>> and then wait till akonadictl status shows it's actually stopped:
>> 
>> Akonadi Control: running
>> 
>> 
>> or you could try:
>> 
>> # killall --user
>> 
>> Kind regards,
>> 
>> Joost
>
>I've tried setting in .xsession:
>
>/usr/bin/akonadictl stop
>killall akonadi_control
>killall kdeinit4
>killall kded4
>
>and various combinations thereof, all of which do not fix the problem. 
>I 
>still have to wait for 90 sec on a black screen before X exits and
>shutdown 
>begins.  :-(
>
>If running first '/usr/bin/akonadictl stop' on a terminal allows X to
>exit, 
>why the same incantation in .xsession does not.  :-/
>
>Is there some other file I can add this command to run when I call for
>X to 
>exit?

Kde and I would assume Gnome as well have a method of running a script when starting and stopping a login session.

This is usually used for ssh-agent and pgp-agent.

You could try looking for something similar with the desktop/window manager of your choice.

I think .xsession is run only during start and will not 'pause' during the session.

--
Joost
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.