From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org)
by nuthatch.gentoo.org with esmtp (Exim 4.62)
(envelope-from <gentoo-user+bounces-58722-garchives=archives.gentoo.org@gentoo.org>)
id 1H81N4-000275-VZ
for garchives@archives.gentoo.org; Fri, 19 Jan 2007 21:34:03 +0000
Received: from robin.gentoo.org (localhost [127.0.0.1])
by robin.gentoo.org (8.13.8/8.13.8) with SMTP id l0JLWqf3028036;
Fri, 19 Jan 2007 21:32:52 GMT
Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.231])
by robin.gentoo.org (8.13.8/8.13.8) with ESMTP id l0JLSVxl004708
for <gentoo-user@lists.gentoo.org>; Fri, 19 Jan 2007 21:28:32 GMT
Received: by wr-out-0506.google.com with SMTP id i28so510131wra
for <gentoo-user@lists.gentoo.org>; Fri, 19 Jan 2007 13:28:31 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=gmail.com; s=beta;
h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
b=bqDHcVpL6G8QbHQ9LC8fOyr2LbrvVdEZ8y4Bip3XGDNTOMH01JjB4zbdH24oRrrq9f/a/751w9xUsjcmDixqfVErvYkZLvPWDmtqaCjbhZgef246fC5WM8cVocZZXARQXCMMvkMzvokWlSdK36QSPKShKtCmvl1qGwMja06H9G8=
Received: by 10.82.139.17 with SMTP id m17mr1159850bud.1169242108210;
Fri, 19 Jan 2007 13:28:28 -0800 (PST)
Received: by 10.82.188.10 with HTTP; Fri, 19 Jan 2007 13:28:28 -0800 (PST)
Message-ID: <bf0e048a0701191328s3986946drc5f1767a554c725f@mail.gmail.com>
Date: Fri, 19 Jan 2007 23:28:28 +0200
From: "Vlad Dogaru" <ddvlad@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Fluxbox/Conky acting up
In-Reply-To: <200701191743.25590.michaelkintzios@gmail.com>
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_Part_145676_11518189.1169242108109"
References: <bf0e048a0701181435s32ff3254ife996b4620aca0cc@mail.gmail.com>
<200701191743.25590.michaelkintzios@gmail.com>
X-Archives-Salt: 3b7cbc3f-a2d5-4ced-b591-8756ef32aba8
X-Archives-Hash: 200ac674b7ad7712bd991582bba58f39
------=_Part_145676_11518189.1169242108109
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On 1/19/07, Mick <michaelkintzios@gmail.com> wrote:
>
> Hi Vlad,
>
> On Thursday 18 January 2007 22:35, Vlad Dogaru wrote:
> > Hello everyone,
> >
> > I had Conky start automatically when I log in to Fluxbox by adding the
> > following line to .fluxbox/startup:
> >
> > exec /usr/bin/conky &
> >
> > It is before exec /usr/bin/fluxbox (a howto warned me about this
> pitfall)
> > and everything works as expected. The only problem is that when I exit
> my
> > Fluxbox session, Conky doesn't stop, but rather starts eating up my CPU
> > (could this be because when I log back in I start another instance of
> it?).
> > It can't be killed with a KILL signal, but I noticed HUP will do the
> trick.
> > Is this normal? How can I have Conky stopped at logout?
>
> Since no answers have been offered so far, I'll have a go at suggesting
> some
> things to try.
>
> I am afraid I do not have conky on my machines, so I can't readily test
> this.
> What you probably need is a line like:
> ============================================
> kill -HUP conky
> ============================================
> after your 'exec /usr/bin/conky &' entry in .fluxbox/startup.
>
> Alternatively,
> ============================================meant to be
> kill -HUP `echo ${SOME_THING} | cut -d ':' -f 2`
> ============================================
> may do the trick but only if 'SOME_THING' is an environment variable for
> conky, which may or may not exist. If it doesn't exist then you need a
> string which will source the conky PID from ps. I haven't such a string
> available here, but I recall seeing something in Google.
>
> Hope the above is not wildly incorrect and helps you find something that
> works. Please post back either way.
Hi Mick,
I've solved the problem by taking your suggestion further. I've added
pkill -HUP conky
to my startup file, before starting Conky. That does the trick as far as I
can tell.
Thanks for the input,
Vlad
--
> Regards,
> Mick
>
>
>
--
How's my English? How about my Netiquette?
Do mail me if something is wrong with my behaviour. Thank you.
------=_Part_145676_11518189.1169242108109
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On 1/19/07, <b class="gmail_sendername">Mick</b> <<a href="mailto:michaelkintzios@gmail.com">michaelkintzios@gmail.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Vlad,<br><br>On Thursday 18 January 2007 22:35, Vlad Dogaru wrote:<br>> Hello everyone,<br>><br>> I had Conky start automatically when I log in to Fluxbox by adding the<br>> following line to .fluxbox/startup:
<br>><br>> exec /usr/bin/conky &<br>><br>> It is before exec /usr/bin/fluxbox (a howto warned me about this pitfall)<br>> and everything works as expected. The only problem is that when I exit my<br>> Fluxbox session, Conky doesn't stop, but rather starts eating up my CPU
<br>> (could this be because when I log back in I start another instance of it?).<br>> It can't be killed with a KILL signal, but I noticed HUP will do the trick.<br>> Is this normal? How can I have Conky stopped at logout?
<br><br>Since no answers have been offered so far, I'll have a go at suggesting some<br>things to try.<br><br>I am afraid I do not have conky on my machines, so I can't readily test this.<br>What you probably need is a line like:
<br>============================================<br>kill -HUP conky<br>============================================<br>after your 'exec /usr/bin/conky &' entry in .fluxbox/startup.<br><br>Alternatively,<br>============================================meant to be
<br>kill -HUP `echo ${SOME_THING} | cut -d ':' -f 2`<br>============================================<br>may do the trick but only if 'SOME_THING' is an environment variable for<br>conky, which may or may not exist. If it doesn't exist then you need a
<br>string which will source the conky PID from ps. I haven't such a string<br>available here, but I recall seeing something in Google.<br><br>Hope the above is not wildly incorrect and helps you find something that<br>
works. Please post back either way.</blockquote><div><br>Hi Mick,<br><br>I've solved the problem by taking your suggestion further. I've added <br><br>pkill -HUP conky<br><br>to my startup file, before starting Conky. That does the trick as far as I can tell.
<br><br>Thanks for the input,<br>Vlad<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">--<br>Regards,<br>Mick<br><br><br></blockquote>
</div><br><br clear="all"><br>-- <br>How's my English? How about my Netiquette? <br>Do mail me if something is wrong with my behaviour. Thank you.
------=_Part_145676_11518189.1169242108109--
--
gentoo-user@gentoo.org mailing list