On 05/09/2011 12:48 PM, Usuário do Sistema wrote:
> disregard my before email! sorry.
> 
> 
> I've just tried:
> 
> 1- export DISPLAY=:0.0
> 
> 2- xauth -f path list
> xauth:  creating new authority file path
> 
> but the same error occur when I run xterm
> 
> Warning: This program is an suid-root program or is being run by the root 
> user.
> The full text of the error or warning message cannot be safely formatted
> in this environment. You may get a more descriptive message by running the
> program as a non-root user or by removing the suid bit on the executable.
> xterm Xt error: Can't open display: %s
> 
> I'dont know very well X Server! so...follow any questions:
> 
> 1- it's necessary a monitor plug in machine full time ?? ( I'm access
> the mechine by ssh and it hasn't monitor )
> 
> 2- I see nothing when I ran "xauth -f path list" neither path to the
> file cookie as you commented below only the message:
>          xauth:  creating new authority file path
> 
> 
> thank!
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 2011/5/9 Marty Jack <marty...@comcast.net>:
>>
>>
>> On 05/09/2011 11:50 AM, Usuário do Sistema wrote:
>>> Hi everyone,
>>>
>>> I'm trying open one session xterm on of the same machine that holds
>>> the X Server but occur a error.
>>>
>>> what I've done:
>>>
>>> 1- login in at the machine that holds the X server by ssh ( the
>>> Machine hasn't monitor )
>>>
>>> 2- ran the command export DISPLAY=0.0
>>>
>>> 3- ran the command xterm
>>>
>>> appear the error follow:
>>>
>>> Warning: This program is an suid-root program or is being run by the root 
>>> user.
>>> The full text of the error or warning message cannot be safely formatted
>>> in this environment. You may get a more descriptive message by running the
>>> program as a non-root user or by removing the suid bit on the executable.
>>> xterm Xt error: Can't open display: %s
>>>
>>> I'm using the Red Hat Enterprise 5.6 on the machine and I need open
>>> one session xterm.
>>>
>>> why occur this error ? what I have do to open xterm session ?
>>>
>>> strangely it was work! out of the blue began appear the message above
>>> when I've ran xterm command.
>>>
>>> any tip it's welcome!
>>>
>>> thank
>>> _______________________________________________
>>> xorg@lists.freedesktop.org: X.Org support
>>> Archives: http://lists.freedesktop.org/archives/xorg
>>> Info: http://lists.freedesktop.org/mailman/listinfo/xorg
>>> Your subscription address: marty...@comcast.net
>>>
>>
>> One thing that looks wrong is it should be DISPLAY=:0.0, you're missing a 
>> colon.
>>
>> The second thing that might be wrong is authorization.  If your Xserver is 
>> started with an -auth switch, you need to export XAUTHORITY=some-path where 
>> that file contains the same session cookie that the server has and is 
>> readable by whatever process is trying to connect to the server.
>>
>> You can poke around with xauth -f path list to see what is in a cookie file 
>> if you need to.
>> _______________________________________________
>> xorg@lists.freedesktop.org: X.Org support
>> Archives: http://lists.freedesktop.org/archives/xorg
>> Info: http://lists.freedesktop.org/mailman/listinfo/xorg
>> Your subscription address: maico...@ig.com.br
>>
> 

Unfortunately I wasn't very clear.  You weren't meant to do the "xauth -f path 
list" blindly.  For one thing "path" was a variable you were supposed to 
provide a sensible value for, and this lists out an authority file you already 
have.  Read "man xauth".

So far you haven't done anything to create the authority file if you need one.  
Do a "ps aux | grep X" and see what your Xserver is being started with.  If it 
has an -auth switch, you need to do something to get the contents of the file 
referenced by the -auth switch into a place where the user can read it and then 
set XAUTHORITY to point to it.

_______________________________________________
xorg@lists.freedesktop.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.freedesktop.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Reply via email to