I've obviously missed something in the explanations of .Xauthority files and MIT cookies. I have two Debian 1.3 machines, foo and bar with 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: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 login as myself, ftp back to foo and copy .Xauthority to bar. On bar, xauth list and xauth list foo/unix:0 both say foo/unix:0 MIT...1 a0b1... but the other forms say nothing. Now I type xeyes -d :0 etc. and :0, unix:0 and foo/unix:0 are all obviously trying to display locally on bar, as the error is 111. xeyes -d foo:0 is refused by the server on foo (an audit message appears on the VC which started X). I presume I have to massage .Xauthority in some way, to create entries for :0, unix:0 and foo:0, but why does .Xauthority have foo/unix:0 put into it by startx? I don't really understand what the syntax foo/unix means and can't find any documentation for it (though I've seen it in examples, e.g. page 82 of Mui and Pearce). -- David Wright, Open University, Earth Science Department, Milton Keynes MK7 6AA U.K. email: [EMAIL PROTECTED] tel: +44 1908 653 739 fax: +44 1908 655 151 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
