Many thanks to the net! My original question:
> After running OpenWindows for a while, connections
> to the display suddenly don't work. This typically happens after
> OpenWindows has been running for an extended period -- say 3 to 4 days --
> without being restarted. Programs that work fine when I leave work will
> bomb the next morning.
The answer is that we have a root process started by cron that deletes
any file in /tmp that's over 3 days old. In addition to deleting all the
legitimate files, this process was also removing the unix-domain socket
in /tmp/.NeWS-unix and /tmp/.X11-unix, thus causing new connections to
":0.0" or "unix:0.0" to stop working. To add to the confusion,
connections to "`hostname`:0.0" still work because the TCP socket is not
in the /tmp namespace.
Making the process overlook the sockets in question has fixed the problem.
Thanks to the following who responded:
Liudvikas Bukys <firstname.lastname@example.org>
Ian MacPhedran <email@example.com>
Dave Sill <firstname.lastname@example.org>
mark galbraith <email@example.com>
Randy Garrett <firstname.lastname@example.org>
Sue Bergquist <email@example.com>
Hope College Department of Computer Science
firstname.lastname@example.org (BITNET: JIPPING@HOPE)
"If is was so, it might be, and if it were so, it would be.
But as it isn't, it ain't. That's logic."
-- Lewis Carroll
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:06:12 CDT