[gentoo-user] Fluxbox/Conky acting up

[gentoo-user] Fluxbox/Conky acting up

[Vlad Dogaru]

[-- Attachment #1: Type: text/plain, Size: 702 bytes --]

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?

Thanks,
Vlad

-- 
How's my English? How about my Netiquette?
Do mail me if something is wrong with my behaviour. Thank you.

[-- Attachment #2: Type: text/html, Size: 776 bytes --]

Re: [gentoo-user] Fluxbox/Conky acting up

[Mick]

[-- Attachment #1: Type: text/plain, Size: 1662 bytes --]

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.
-- 
Regards,
Mick

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Fluxbox/Conky acting up

[Vlad Dogaru]

[-- Attachment #1: Type: text/plain, Size: 2086 bytes --]

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.

[-- Attachment #2: Type: text/html, Size: 2764 bytes --]

Re: [gentoo-user] Fluxbox/Conky acting up

[Mick]

[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]

On Friday 19 January 2007 21:28, Vlad Dogaru wrote:
> On 1/19/07, Mick <michaelkintzios@gmail.com> wrote:

> > 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.

> 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.

Try adding it after the start fluxbox line.  Then it should kill it when 
fluxbox exits.

PS. Your English is perfect and so would be your netiquette, especially if you 
posted messages in plain text only!  ;-)
-- 
Regards,
Mick

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Fluxbox/Conky acting up

[Vlad Dogaru]

[-- Attachment #1: Type: text/plain, Size: 1603 bytes --]

On 1/20/07, Mick <michaelkintzios@gmail.com> wrote:
>
> On Friday 19 January 2007 21:28, Vlad Dogaru wrote:
> > On 1/19/07, Mick <michaelkintzios@gmail.com> wrote:
>
> > > 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.
>
> > 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.
>
> Try adding it after the start fluxbox line.  Then it should kill it when
> fluxbox exits.


Never thought of it that way, but I will give ti a try.

PS. Your English is perfect and so would be your netiquette, especially if
> you
> posted messages in plain text only!  ;-)


That's a problem I have. Can I configure Gmail to send plain text?

Thanks,
Vlad

--
> Regards,
> Mick
>
>
>


-- 
How's my English? How about my Netiquette?
Do mail me if something is wrong with my behaviour. Thank you.

[-- Attachment #2: Type: text/html, Size: 2515 bytes --]

Re: [gentoo-user] Fluxbox/Conky acting up

[Vlad Dogaru]

On 1/20/07, Vlad Dogaru <ddvlad@gmail.com> wrote:
> On 1/20/07, Mick <michaelkintzios@gmail.com> wrote:
>
> >  On Friday 19 January 2007 21:28, Vlad Dogaru wrote:
> > > On 1/19/07, Mick <michaelkintzios@gmail.com> wrote:
> >
> > > > 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.
> >
> > > 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.
> >
> > Try adding it after the start fluxbox line.  Then it should kill it when
> > fluxbox exits.
>
>
> Never thought of it that way, but I will give ti a try.
>
>
> >  PS. Your English is perfect and so would be your netiquette, especially if you
> > posted messages in plain text only!  ;-)
>
>
> That's a problem I have. Can I configure Gmail to send plain text?

Never mind that, I was just being idiotic thinking it was some sort of
hack. The link in the formatting bar had completely eluded me for
years.

Vlad
>
>
> > --
> > Regards,
> > Mick
> >
> >
> >
>
>
>
>
> --
> How's my English? How about my Netiquette?
> Do mail me if something is wrong with my behaviour. Thank you.



-- 
How's my English? How about my Netiquette?
Do mail me if something is wrong with my behaviour. Thank you.
-- 
gentoo-user@gentoo.org mailing list