Subject: Re: trouble with sockets
To: None <current-users@NetBSD.ORG>
From: Charles Hannum <mycroft@deshaw.com>
List: current-users
Date: 01/04/1996 01:17:12
In article <199601031444.IAA02688@orac.ece.utexas.edu>
chase@orac.ece.utexas.edu (Craig M. Chase) writes:
About once a week I need to reboot my NetBSD-current (i386) box
because I get the following error:
chase@orac>xterm
TRANS(SocketUNIXConnect) () can't connect: errno = 2
The X server (XFree86-3.1.2A) seems to simply be unwilling to accept
any new connections. Any X client causes the same behavior, e.g.,
chase@orac>xclock
TRANS(SocketUNIXConnect) () can't connect: errno = 2
This sort of thing usually occurs because some automatic reeper
deleted the Un*x-domain socket to the X server, which is stored in
/tmp/.X11-unix/.