no its still not working
UID PID PPID C STIME TTY TIME CMD
c0re 21688 1 8 23:35 ? 00:00:22 python /usr/lib/exaile/exaile.py
I get the same (I was expecting different should have checked at this end first...):
But if I run "ps -C exaile" I get:Code:UID PID PPID C STIME TTY TIME CMD mark 4390 1 7 18:03 ? 00:00:00 python /usr/lib/exaile/exaile.py
which is probably why if_running works for me.Code:PID TTY TIME CMD 4390 ? 00:00:00 exaile
I am running exaile v.0.2.14
.................?
look what i have found... easy way to change exaile's process name
http://code.google.com/p/procname/
Yes, but I get the exact same ps output as you do, I'm running the exact same version of Exaile as you are, and it doesn't work for me.
Not that I wouldn't be delighted to have $if_running work as advertised (or as I think it should), but I've got a snazzy work around for my issue, thanks to the folks over on #conky, but I still don't understand why we'd all get different results from the exact same thing.
I'm running conky 1.6.1, from the Intrepid repos.
In other news, I've noticed an interesting "glitch" in the interaction between exaile and conkyExaile. I don't think that it has anything to do with conkyExaile, but in case it does, I wanted to mention it...
I've noticed that when exaile is left paused for extended periods of time -- like overnight -- the track info displayed in conky will disappear (i.e. go blank). If I open exaile and look at the UI, it still shows the paused track sitting there, so I'm guessing that somehow, the communication stream (DBUS?) between exaile and conky is hiccuping.
Does this sound right? Ever see it before?
I can't figure out the if_running issue, makes no sense to why why it's not working for you.
mmmmm, that overnight glitch certainly points towards dbus...
In the morning when you see this behaviour, what happens is you stop and start conky again, do you see the correct info again?
Bookmarks