[comp.windows.x] xinit and -DUNIXCONN

dinah@WILKINS.BCM.TMC.EDU (Dinah McNutt Anderson) (09/13/90)

I had a user complaining because DISPLAY was always getting set to
unix:0.0 on his SPARCstation regardless of what he did in his .login file.
Some poking around turned up that xinit was setting the DISPLAY to 
unix:0.0 when UNIXCONN was defined. This is one of the default values
for ConnectionFlags in Project.tmpl which is referenced in xinit's Imakefile. 
I have  several questions.

1) What else is UNIXCONN used for? I looked in the doc directory and
   could not find it referenced anywhere.

2) Why is this the default? 

3) What are the consequences of undefining it? I figure the only workstations
   you wouldn't want DISPLAY set to the hostname would be X-terminals and
   we don't run xinit on them anyway.

Thanks,

Dinah Anderson

klee@wsl.dec.com (Ken Lee) (09/13/90)

In article <9009121845.AA06252@NICOLLE.IAIMS.BCM.TMC.EDU>, dinah@WILKINS.BCM.TMC.EDU (Dinah McNutt Anderson) writes:
|> 1) What else is UNIXCONN used for? 

Among other things, Xlib uses UNIXCONN to determine whether or not to
support UNIX-domain sockets.

|> 2) Why is this the default? 

UNIX-domain sockets are usually the most efficient type of connection
so you want to support and use them when you can.

|> 3) What are the consequences of undefining it?

Xlib will not be able create UNIX-domain socket connections to the X server.

-- 
Ken Lee
DEC Western Software Laboratory, Palo Alto, Calif.
Internet: klee@wsl.dec.com
uucp: uunet!decwrl!klee