From owner-freebsd-questions  Mon Sep 22 12:17:03 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id MAA10767
          for questions-outgoing; Mon, 22 Sep 1997 12:17:03 -0700 (PDT)
Received: from horton.iaces.com (proot@horton.iaces.com [204.147.87.98])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA10758
          for <questions@FreeBSD.ORG>; Mon, 22 Sep 1997 12:16:56 -0700 (PDT)
Received: (from proot@localhost)
	by horton.iaces.com (8.8.5/8.8.5) id OAA18281;
	Mon, 22 Sep 1997 14:16:52 -0500 (CDT)
From: "Paul T. Root" <proot@horton.iaces.com>
Message-Id: <199709221916.OAA18281@horton.iaces.com>
Subject: Re: PPP and X ?!?
To: patrick@cre8tivegroup.com (Patrick Gardella)
Date: Mon, 22 Sep 1997 14:16:51 -0500 (CDT)
Cc: questions@FreeBSD.ORG, brian@awfulhak.com.acs.uswest.com
In-Reply-To: <XFMail.970922132433.patrick@cre8tivegroup.com> from Patrick Gardella at "Sep 22, 97 01:12:17 pm"
X-Organization: !nterprise Networking Services - ACES
X-Phone: (612) 664-3385
X-Fax: (612) 664-4779
X-Page: (800) SKY-PAGE PIN: 537-7270
X-Address: 600 Stinson Blvd, Fl 1S
X-Address: Minneapolis, MN 55413
X-Mailer: ELM [version 2.4ME+ PL22 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

In a previous message, Patrick Gardella said:
> Here is a strange error...
> 
> 
> If I go the other way around, starting ppp (dialing out) as I startx, I freeze 
> up ppp (which I can then kill and restart).
> 
> If I startx, and then start ppp no problem.
> 
> Nothing shows up in /var/log/ppp.log, by the way besides the normal messages ]
> (LCP IPCP CCP).
> 
> This happened with the standard 2.2.1 release of X and PPP as well.  I upgraded
> to the latest to see if that would work.
> 
> I'm not sure how they are related.  Any other pertinent info needed?
> 
> Patrick
> 
> P.S.  This is very easy to prevent, so I am able to work around it.  It's just 
> annoying when I forget ;)
> 


I had the opposite problem, but maybe it's the same sort of thing. 
Mine turned out to be the machine was trying to do dns resolution and
was timing out without the interface up. Is hosts before dns in your
/etc/host.conf file? A good way to see what's happening is to run tcpdump on 
tun0 while you try to bring up X. Then you can see what's happening on
the interface. 

Also check /etc/X0.hosts. and .xsession.errors in your home directory.


-- 
Oh, my friend, it's not what they take away from you that counts.  Its's
what you do with what you have left.  --Hubert Humphrey