What controls what appears when you 'w'? I just noticed that when I am in
X and I 'w' all my X terms are from unix:0 instead of plain old :0 like
they used to be. extace doesn't work with unix:0, it just likes :0. Is
there a non destructive way I can chan
with few changes from how things
> > install themselves. I start X as user myself on foo. Typing xauth list
> > says foo/unix:0 MIT...1 a0b1... and so does xauth list :0 and xauth list
> > unix:0 and xauth foo/unix:0 but not xauth foo:0 which says nothing.
[...]
> > Now
/unix:0 MIT...1 a0b1... and so does xauth list :0 and xauth list
unix:0 and xauth foo/unix:0 but not xauth foo:0 which says nothing.
If I su to root and copy ~myself/.Xauthority to ~root I can run xeyes with
xeyes -d :0 etc., but not xeyes -d foo:0 which is refused.
Now I telnet to bar and log
as user myself on foo. Typing xauth list
>says foo/unix:0 MIT...1 a0b1... and so does xauth list :0 and xauth list
>unix:0 and xauth foo/unix:0 but not xauth foo:0 which says nothing.
Assuming foo is your local machine, what happens if you do xhost +bar then
telnet to bar, export DISPLAY=
> > >essentially identical configurations, with few changes from how things
> > >install themselves. I start X as user myself on foo. Typing xauth list
> > >says foo/unix:0 MIT...1 a0b1... and so does xauth list :0 and xauth list
> > >unix:0 and xauth foo/unix
s user myself on foo. Typing xauth list
> says foo/unix:0 MIT...1 a0b1... and so does xauth list :0 and xauth list
> unix:0 and xauth foo/unix:0 but not xauth foo:0 which says nothing.
>
> If I su to root and copy ~myself/.Xauthority to ~root I can run xeyes with
> xeyes -d :0 etc., but
ns, with few changes from how things
> >install themselves. I start X as user myself on foo. Typing xauth list
> >says foo/unix:0 MIT...1 a0b1... and so does xauth list :0 and xauth list
> >unix:0 and xauth foo/unix:0 but not xauth foo:0 which says nothing.
>
> Assuming fo
7 matches
Mail list logo
