From owner-freebsd-questions@FreeBSD.ORG Wed Oct 15 16:33:40 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 10A86AC9 for ; Wed, 15 Oct 2014 16:33:40 +0000 (UTC) Received: from mail-wi0-f179.google.com (mail-wi0-f179.google.com [209.85.212.179]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7E537E49 for ; Wed, 15 Oct 2014 16:33:38 +0000 (UTC) Received: by mail-wi0-f179.google.com with SMTP id d1so2421339wiv.12 for ; Wed, 15 Oct 2014 09:33:37 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:mime-version:content-type:content-disposition :user-agent; bh=NLfTYVhq6I7HcLPrJlOCKfz3eQpnmquca/ZZnaotpzw=; b=ZcJHhT6etrsW9wzdzqZquzZ6dJ7HL4l7V8kig13HQhSNDy3cHGn7hKwvc7L2MSLQt0 h9jGCUe4RGwE3WaoI6LOFSMFcwI4f8Ku4CaFh9jK/PYXNrskVlRRLKTE+y6rkVZfqytg 8IykHi7RGyTFI6wFLTSXRQQjjmt+oLoXo63keEehCGeFwUyzZ2GSyQf4nQbOW9hP57hw 2wMejkxQLaF682PL+4StmNLV4aQicLTioHvbq0GRd+yMVgetCYzCh6O9Ga3z9PKeu8Dh vTa9UrVsOKAmzfsiFhO3IQWdu95RY58osk7xPBHT0fznFyzXZ00TvNxm1KC1vplMLO4C S0Rw== X-Gm-Message-State: ALoCoQkWFKEVOsyyQK9KmpNkGs1+yDUdZ+zXmZjkqwEswajXRQfK50BgWYgRaGjennwzMHwpjIof X-Received: by 10.180.75.179 with SMTP id d19mr13529167wiw.21.1413390504212; Wed, 15 Oct 2014 09:28:24 -0700 (PDT) Received: from localhost (itcom245.staff.itd.umich.edu. [141.213.135.249]) by mx.google.com with ESMTPSA id wc7sm17550327wjc.8.2014.10.15.09.28.23 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Oct 2014 09:28:23 -0700 (PDT) Date: Wed, 15 Oct 2014 12:25:47 -0400 From: William Bulley To: Polytropon Subject: Re: exiting Xorg locks up 9.2-STABLE system Message-ID: <20141015162547.GJ3963@itcom245.staff.itd.umich.edu> Mail-Followup-To: Polytropon , freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Oct 2014 16:33:40 -0000 According to Polytropon on Wed, 10/15/14 at 12:18: > > The last line of your ~/.xinitrc file should be: > > exec /usr/local/bin/mwm > > This makes sure that the process "continues" as mwm, and when > mwm exits, then X also exists. Thanks. The last line of my ~/.xinitrc file is: /usr/local/bin/mwm 2>&1 /dev/null and since I start Xorg thusly: /usr/local/bin/xinit -- /usr/local/bin/Xorg I had thought when I exit mwm(1) using the "f.quit_mwm" feature, that then Xorg would exit. Is that not the case? Or am I missing your point above? This configuration has been working for me for about fifteen years. :-) Regards, web... -- /"\ ASCII RIBBON / William Bulley \ / CAMPAIGN AGAINST / X HTML E-MAIL AND / E-MAIL: web@umich.edu / \ LISTSERV POSTINGS / 72 characters width template ----------------------------------------->|