Trouble Shooting: Not authorized to use display

    If you get error messages that look like
	Xlib:  connection to ":0.0" refused by server
	Xlib:  Internal error during connection authorization check
	Error: Can't Open display
    try, on the machine running OpenWindows or X11,
	xhost +machine
    where "machine" is the computer on which you ran the command that failed.
    If you want to let other users run programs on the same machine as you,
    using your display, you will have to type the bizarre-looking
	xhost +`hostname`
    (or xhost +happyboy, if happyboy is the name of your workstation).
    This lets ANY user on `happyboy' access your display.

    With OpenWindows 3 you can also use xauth, and the Programmer's Guide 
    describes how to do this in Chapter 8, p. 101.  This is more secure.
    Also check the man page for fbtab(5) to stop other users accessing the
    framebuffer directly!

    Also note that there is a Sun patch for OpenWindows 3.0 under SunOS 4.1.1
    to fix a serious security problem.  It is available through your local
    Sun Answer Center as well as through anonymous ftp from ftp.uu.net
    [192.48.96.2] system in /sun-dist:
    Fix                     PatchID        Filename            Checksum
    loadmodule              1076118        100448-01.tar.Z     04354  5

    On an X Terminal, there may be a setup menu that lets you change or
    disable the list of hosts that can access the display.

    If you start getting this message after you've been logged in overnight,
    there might be a cron job that's removing the Unix sockets in /tmp
    that are used to communicate with the server when $DISPLAY doesn't have
    a hostname before the :, or is empty.  Have the system administrator
    change the cron script to skip sockets, or log out when you go home!