Date: Sun, 25 Jun 2023 16:21:02 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> To: Hiroki Tagato <tagattie@FreeBSD.org>, FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: Is it possible to build node package as single executable binary? Message-ID: <b712e558-331b-69d3-e48e-ec0faed283f0@quip.cz> In-Reply-To: <898f8065-1544-e157-6139-4f1269ab6ddb@FreeBSD.org> References: <c50228d7-63c7-0e5c-7b38-d9e4c5a3e795@quip.cz> <5be6c0d2-5d71-38c9-028a-8ce065102be9@FreeBSD.org> <c252b857-8657-843f-7619-e5ec55b1c9db@quip.cz> <898f8065-1544-e157-6139-4f1269ab6ddb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 25/06/2023 10:21, Hiroki Tagato wrote: > Hi, [..] >> Do you know why this packaged "bw" needs /tmp to be executable while >> "bw" installed by "npm install" works with noexec set on /tmp? > > It appears native node modules have to be written on the disk before > being executed. There is an explanatory comment at the following URL: > https://github.com/vercel/pkg/blob/main/prelude/bootstrap.js#L2208 > >> Is there a way to fix it? I really would like to keep /tmp noexec. > > The path the native module written to seems TMPDIR-aware. So one > workaround would be setting TMPDIR somewhere other than "/tmp". Thank you for the explanation, you are right. I tested it on Debian now at it failed the same way. I will remount /tmp or will try to push TMPDIR env in to scripts using "bw". Kind regards Miroslav Lachman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b712e558-331b-69d3-e48e-ec0faed283f0>