Date: Wed, 13 Apr 2022 12:04:26 +0000 From: bugzilla-noreply@freebsd.org To: rc@FreeBSD.org Subject: [Bug 235185] /etc/rc.d/ environment may need to be cleaned vs services(8) Message-ID: <bug-235185-20181-3oDDWX7Mlw@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-235185-20181@https.bugs.freebsd.org/bugzilla/> References: <bug-235185-20181@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D235185 Mateusz Kwiatkowski <kwiat3k@panic.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kwiat3k@panic.pl --- Comment #44 from Mateusz Kwiatkowski <kwiat3k@panic.pl> --- One more data point to this issue: software installed from ports that depen= d on looking binaries in PATH, behaves differently when started with service(8) = or directly with rc script. One example is containerd + runj. Containerd is a container runtime whereas runj is a "plugin" to make it work with FreeBSD Jails. Runj is installed by ports and its binary is located in /usr/local/bin/ which is not included in default PATH set by service(8) or /etc/rc. Without setting PATH explicitly in a rc script, containerd will wo= rk when started by script and won't work when started by service(8) or after reboot. I think that it's annoying inconsistency. My vote goes to sanitising environment in every case, starting with next major release. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-235185-20181-3oDDWX7Mlw>