Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 02 Mar 2016 18:23:39 -0800
From:      "Chris H" <bsd-lists@bsdforge.com>
To:        <freebsd-stable@freebsd.org>
Subject:   Re: Why must X open TCP by default?
Message-ID:  <f4ba1f200eb0c96a52ca21ce2efc875c@ultimatedns.net>
In-Reply-To: <20160303015011.GB7329@neutralgood.org>
References:  <e703d257971642a10c95ef53dc9ea4f4@ultimatedns.net> <CAOjFWZ4q=AKxuA_RH_KCGz4wrTTcMr%2B_VVjYxbZ6ayQTN1pfxQ@mail.gmail.com> <38daa5ebf8d9d06b5595ff8da54cc18c@ultimatedns.net> <CAKFCL4U_i1t-NQB6tXsmiSPUHi0AgPB2zO1AtM4wb41VvkmdhQ@mail.gmail.com> <4d19e06d7d2c32801a10011cbd46e2e7@ultimatedns.net>, <20160303015011.GB7329@neutralgood.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2 Mar 2016 20:50:11 -0500 kpneal@pobox.com wrote

> On Wed, Mar 02, 2016 at 02:54:53PM -0800, Chris H wrote:
> > #!/bin/sh -
> > /usr/local/bin/startx -- -nolisten tcp
> > 
> > exit
> > 
> > which seems to get the job done, and allow me to be lazy
> > at the CLI. :-)
> 
> Personally, I'd go with:
> 
> #!/bin/sh -
> exec /usr/local/bin/startx -- -nolisten tcp
> 
> Because then I have one fewer processes running cluttering up my ps listings,
> and because the exit code from startx will now naturally be picked up by
> the parent program. What if, for example, startx crashes? Your script
> will hide that fact. With exec no information is lost.

Crap. Good point(s); points I should have already recognized.
I'm apparently not firing on all cylinders today.
Thanks, Neal, for taking the time to give me a Wake Up call! :-)

> 
> -- 
> Kevin P. Neal                                http://www.pobox.com/~kpn/

--Chris





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f4ba1f200eb0c96a52ca21ce2efc875c>