tag:blogger.com,1999:blog-7700475954028247590.post7555823840037480470..comments2019-10-14T06:37:12.762+01:00Comments on an openSUSE blog: simple qdbus tutorial (part two)cmhttp://www.blogger.com/profile/02884362823199436058noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-7700475954028247590.post-62624139582521182942010-11-10T13:20:53.162+00:002010-11-10T13:20:53.162+00:00Nice work!
I ran into a problem ... 'pidof kd...Nice work!<br /><br />I ran into a problem ... 'pidof kded4' spits out to pids which breaks the script. i guess 1 id is plenty so a quick regex should do the trick but I wanted to know if there is some underlying importance which pid is used. do you have some information on that?Unknownhttps://www.blogger.com/profile/17883595327657726844noreply@blogger.comtag:blogger.com,1999:blog-7700475954028247590.post-43993327672590950942009-05-06T10:47:00.000+01:002009-05-06T10:47:00.000+01:00Excellent, Nate - thank you. I still wonder why it...Excellent, Nate - thank you. I still wonder why it can't be a little more intuitive.cmhttps://www.blogger.com/profile/02884362823199436058noreply@blogger.comtag:blogger.com,1999:blog-7700475954028247590.post-91646662508438198562009-05-06T05:09:00.000+01:002009-05-06T05:09:00.000+01:00Thanks to a combination of your tips and some tips...Thanks to a combination of your tips and some tips I read somewhere else, I can now do this quickly and easily. Just put the following command in a file that gets sourced on login, such as ~/.bashrc for example.<br /><br />alias getdbus="export DBUS_SESSION_BUS_ADDRESS=`cat /proc/$(pidof kded4)/environ | tr '\0' '\n' | grep DBUS | cut -d '=' -f2-`"<br /><br />Since I use kde, kded4 is a process that will always be running, but this may need to be changed. Then once you ssh into your remote computer, just type "getdbus" and voila!snowboarder13https://www.blogger.com/profile/09848714309197245997noreply@blogger.com