Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 15 Oct 2014 18:53:27 +0200
From:      Polytropon <>
To:        William Bulley <>
Subject:   Re: exiting Xorg locks up 9.2-STABLE system
Message-ID:  <>
In-Reply-To: <>
References:  <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Wed, 15 Oct 2014 12:25:47 -0400, William Bulley wrote:
> 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.   :-)

Interesting, but it's not what The FreeBSD Handbook suggests
and what _I_ have been using for about fifteen years. :-)

The "exec" statement makes the xinit process "continue" as
the window manager process. Its f.quit_mwm function exits
the mwm program, but that does not have any effect on the
X session - the session continues without a window manager
(which is possible). Only if the X process is "connected"
to the window manager process using "exec", it will exit,
and so quit the X session entirely.

This is what "init" or "startx" help to do: They source
the .xinitrc file and execute it. Its last line, the "exec"
statement, creates the "connection" between the X session
and the program which has control over its life, usually
the window manager - but it could also be an xterm, and
when _that_ xterm is closed, the X session terminates.
The line "exec /usr/local/bin/mwm" will do this.

More details here:

Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...

Want to link to this message? Use this URL: <>