Date: Sat, 11 Dec 2021 12:59:15 +0300 From: Gleb Popov <arrowd@freebsd.org> To: "Daniel O'Connor" <darius@dons.net.au> Cc: freebsd-hackers <freebsd-hackers@freebsd.org> Subject: Re: What to use in place of abstract unix sockets? Message-ID: <CALH631nVvp2Ra4RYzEpPkQ-bi_sgqiQ5_XxrP35mTx=8R7dODg@mail.gmail.com> In-Reply-To: <58874E76-8541-46BF-A197-C984D6A869DF@dons.net.au> References: <CALH631kYAz%2B_=p6VUhxzx0tz8eox804PCK5A9POxQkZTdThZCQ@mail.gmail.com> <F0BE714E-E25B-4A49-AA6E-B0E906374446@dons.net.au> <CALH631m8P_NG3nTZ1JQ2hhZMTrAMuuGjS8Ahz_qDMu1bFDCzkw@mail.gmail.com> <58874E76-8541-46BF-A197-C984D6A869DF@dons.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
--000000000000f637db05d2dbe5c0 Content-Type: text/plain; charset="UTF-8" On Fri, Dec 10, 2021 at 12:09 PM Daniel O'Connor <darius@dons.net.au> wrote: > > > > On 10 Dec 2021, at 18:23, Gleb Popov <arrowd@freebsd.org> wrote: > > > What can I do to make this software work for FreeBSD? Simply using > regular > > > UDS instead of abstract ones doesn't work for obvious reasons - the > > > "client" can't find the socket file. > > > > If the parent knows where the child will chroot it could create a unix > domain socket under that directory somewhere. > > > > Same problem as above - there should be a single socket on the erver > side. > > I just did a quick test with nc and you can hard link unix domain sockets > so you could bind it in the parent then hard link it for each child. > > Seems pretty kludgy though :) > This is actually a nice suggestion, as it is simple to try out. However, it doesn't work, the link() call fails with EXDEV: Cross-device link This might be because the chroot's target directory is an nullfs mount. Am I right that it isn't possible to create hard links that span nullfs mount points? --000000000000f637db05d2dbe5c0--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALH631nVvp2Ra4RYzEpPkQ-bi_sgqiQ5_XxrP35mTx=8R7dODg>