>Date: Fri, 14 Nov 1997 18:28:02 +0000 (GMT)
>From: John Pelan <johnp@am.qub.ac.uk>
>X-Sender: johnp@phantom
>Reply-To: J.Pelan@am.qub.ac.uk
>Mime-Version: 1.0
>Content-Type: TEXT/PLAIN; charset=US-ASCII
>Sender: port-pmax-owner@NetBSD.ORG
>Precedence: list
>Delivered-To: port-pmax@NetBSD.ORG
>
>
>On Fri, 14 Nov 1997, emanuel stiebler wrote:
>
>> i have exact the same problem with xfs. started manually is ok, but setting
>> xfs=YES in rc.conf freezes the system.
>
>Ok, I too can demonstrate this problem, however by postponing the
>initialization of xfs until *after* inetd all seems well...

I moved xfs to after inetd in /etc/rc, and it made no difference.

I did find two distinct workarounds.  Before starting X, do one of the
two following things:

- telnet to port 7100 and press return

- send a HUP signal to xfs

If you forget to do one of those, telnet into the box, kill -9 the X
process, and rerun startx.  It will work the second time.

The output of "netstat -Aa | grep 7100" while in this stuck state is
interesting:

c0491500 tcp        0      0  localhost.1025     localhost.7100     CLOSE_WAIT
c0485a00 tcp        0      0  *.7100             *.*                LISTEN
c0485400 stream      0      0 c0486e80        0        0        0 /tmp/.font-unix/fs7100

(that socket has been CLOSE_WAIT for about 20 minutes)

Hopefully, this information will help someone with a clue to find a
real fix.

Cheers,
entropy

--
entropy -- it's not just a good idea, it's the second law.