Date: Wed, 2 Mar 2016 15:59:57 -0500 From: Brandon Allbery <allbery.b@gmail.com> To: Chris H <bsd-lists@bsdforge.com> Cc: freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: Why must X open TCP by default? Message-ID: <CAKFCL4U_i1t-NQB6tXsmiSPUHi0AgPB2zO1AtM4wb41VvkmdhQ@mail.gmail.com> In-Reply-To: <38daa5ebf8d9d06b5595ff8da54cc18c@ultimatedns.net> References: <e703d257971642a10c95ef53dc9ea4f4@ultimatedns.net> <CAOjFWZ4q=AKxuA_RH_KCGz4wrTTcMr%2B_VVjYxbZ6ayQTN1pfxQ@mail.gmail.com> <38daa5ebf8d9d06b5595ff8da54cc18c@ultimatedns.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 2, 2016 at 3:56 PM, Chris H <bsd-lists@bsdforge.com> wrote: > Good catch, by both you, and Brandon. I just tried it. But > sockstat(1) still reports 6000 being open. Closing the X > server, and session, reveal that 6000 is no longer open. > Bummer. > Check `man 7 Xserver` to verify the option needed. You might also have to check the xserverrc file (I don't recall where it is offhand and can't really check right now, but startx is a shell script and the default xserverrc will be set near the top) to see if it is overriding the option. In that case you could copy the xserverrc to ~/.xserverrc (make sure it's chmod +x) and edit that copy to force nolisten tcp, or for multiple users you'd edit the master xserverrc but may need to remember to re-edit after system updates. -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKFCL4U_i1t-NQB6tXsmiSPUHi0AgPB2zO1AtM4wb41VvkmdhQ>