sudo with problems

[Uwe Dippel]

--- William Hooper <whooper@freeshell.org> wrote:

> The error is coming from xauth, not VNC.

> Is there a reason to use sudo over just using su?  The init scripts
> from
> both TightVNC and Red Hat (possibly more) use su without a problem. 

Sorry, here they don't.
I tried 
[root@machine myuser]# su - myuser -c "vncserver :1"
xauth:  timeout in locking authority file /root/.xauthGPeKe5
xauth:  timeout in locking authority file /root/.xauthGPeKe5

> Check
> out http://faq.gotomyvnc.com/fom-serve/cache/86.html for a copy of
> Red
> Hat's script.

I did. It takes a whole of a lot of time more until the [OK] shows up
than natively. Precisely the same time as waiting for sudo / su. Only,
the script somehow directs those messages to /dev/null.
Can someone else try starting a simple 
$ vncviewer :12
?? It should be up in a second or two (here it is four, to be precise)
$ /etc/rc.d/init.d/vncviewer start
should take about 45 seconds. Just as long as the su or sudo.

Uwe

__________________________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo
http://search.yahoo.com