1 |
Hi, |
2 |
|
3 |
>Von: Boyd Stephen Smith Jr. [mailto:bss03@××××××××××.net] |
4 |
>Gesendet: Di 9/26/2006 3:56 |
5 |
>An: gentoo-user@l.g.o |
6 |
>Betreff: Re: [gentoo-user] Question about the dcop utility: How to use it from a remote computeR? |
7 |
<snip> |
8 |
|
9 |
>I've never used DCOP, but I figured this was probably related to |
10 |
>environment variables, so I did an strace on a simple dcop invocation to |
11 |
>try and figure out why it can't find the (presumably) running dcop server |
12 |
>on "O". |
13 |
|
14 |
>On my system communication with the local DCOP server is via |
15 |
>~/.DCOPserver_<hostname>__0, and I'm fairly sure the _0 at the end |
16 |
>corresponds to part of my DISPLAY setting, ":0", indicating a local X |
17 |
>server. You may need to set your DISPLAY environment variable on "O" |
18 |
>before you do the dcop invocation. |
19 |
|
20 |
>Assuming "O" is a standard desktop machine and you are the only one logged |
21 |
>on to it, you should be able to do something like: |
22 |
>ssh O env DISPLAY=:0.0 dcop |
23 |
>to get the standard dcop output. |
24 |
|
25 |
THANK YOU! That worked like a charm! |
26 |
Problem solved.. |
27 |
The only sure-fire way to determine the correct DISPLAY setting is to pull |
28 |
it from the X session you want to connect to. E.g.: |
29 |
$ env | grep ^DISPLAY |
30 |
DISPLAY=:0.0 |
31 |
|
32 |
-- |
33 |
"If there's one thing we've established over the years, |
34 |
it's that the vast majority of our users don't have the slightest |
35 |
clue what's best for them in terms of package stability." |
36 |
-- Gentoo Developer Ciaran McCreesh |