Date sent: 26-APR-1996 09:07:49
Hello!
Below is the answer to the problem that I was having with OpenWindows.
After installing the kernel patch, I could successfully startup OpenWindows.
Many, many thanks to Mike for all of his help in solving this problem!
************************************************************************
** Debbie Jordan ** **
** ENZIAN Technology, Inc. ** **
** Naval Surface Warfare Center - Dahlgren Division ** **
** 17137 Dahlgren Rd. ** **
** Dahlgren, VA 22448 ** **
** Office: (540) 653-4769 ** **
** Fax: (540) 653-1810 ** **
** Internet: djordan@relay.nswc.navy.mil ** **
************************************************************************
From: UNODE2::WINS%"<lists@impaqt.drexel.edu>" 25-APR-1996 10:55:18.99
To: SYSTEM SUPPORT <SYSTEM_DJ@unode2.nswc.navy.mil>
CC:
Subj: Re: Please help with OpenWindows 3.3 problem
Return-Path: <lists@impaqt.drexel.edu>
Received: from impaqt.drexel.edu by unode2.nswc.navy.mil with SMTP ;
Thu, 25 Apr 96 10:54:34 EST
Received: by impaqt.drexel.edu (4.1/SMI-4.1)
id AA03355; Thu, 25 Apr 96 10:52:34 EDT
Date: Thu, 25 Apr 1996 10:51:14 -0400 (EDT)
From: List Subscriber <lists@impaqt.drexel.edu>
Sender: List Subscriber <lists@impaqt.drexel.edu>
eply-To: List Subscriber <lists@impaqt.drexel.edu>
Subject: Re: Please help with OpenWindows 3.3 problem
To: SYSTEM SUPPORT <SYSTEM_DJ@unode2.nswc.navy.mil>
In-Reply-To: <199604232048.PAA08546@ra.mcs.anl.gov>
Message-Id: <Pine.3.87.9604251045.A3336-0100000@cerebrum>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Debbie:
I think I've seen your problem before. Suggestions are below.
Hope they help.
Mike
On 23 Apr 1996, SYSTEM SUPPORT wrote:
Binding Unix socket: Invalid argument
Fatal server error:
Cannot establish unix listening socket
/usr/openwin/bin/xinit: Server error.
When attempting to start OpenWindows, it can fail with the message:
"Cannot establish unix listening socket"
Although this error message is issued by X library code, it is due
to a problem with the socket library.
Two causes have been identified:
1) The system starting OpenWindows obtains OpenWindows from another
solaris server running a different version of the kernel jumbo patch.
On Solaris 2.3 that is 101318
On Solaris 2.4 that is 101945 (sparc version)
This problem is not well understood, but certainly libsocket is
part of the kernel jumbo patch.
This may apply where the serveris just an NFS server, or where
it is a boot server.
In this scenario, probably no user will be able to start OpenWindows.
2) The permissions on the TLI special device files used by the socket
library are incorrect. In this case, "root" willbe able to
start OpenWindows, but not any other user.
Permissions SHOULD appear as below:
# cd /devices/pseudo
# ls -l clone@0:t
crw-rw-rw- 1 root sys 11, 42 Feb 15 17:11 clone@0:tcp
crw-rw-rw- 1 root sys 105, 2 Feb 15 17:11 tl@0:ticlts
crw-rw-rw- 1 root sys 105, 0 Feb 15 17:11 tl@0:ticots
crw-rw-rw- 1 root sys 105, 1 Feb 15 17:11 tl@0:ticotsord
If other users do not have read/write access, this must be fixed.
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:10:58 CDT