Date: Wed, 23 Oct 2024 10:16:41 +0000 From: bugzilla-noreply@freebsd.org To: rc@FreeBSD.org Subject: [Bug 282255] rc: Is rc_fast_and_loose actually working? Message-ID: <bug-282255-20181-1PExRJlhPM@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-282255-20181@https.bugs.freebsd.org/bugzilla/> References: <bug-282255-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=3D282255 Mateusz Piotrowski <0mp@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Open |In Progress Assignee|rc@FreeBSD.org |0mp@FreeBSD.org --- Comment #6 from Mateusz Piotrowski <0mp@FreeBSD.org> --- With rc_fast_and_loose=3Dyes,rc(8) on my system stops processing rc service= s as early as rc.d/hostid, which calls exit 0. That's before my machine even sets its hostname properly. As a result, I get a login prompt saying that I've booted Amnesiac. I cannot even log in because I get "pam_open_session(): Sessions failure". Technically, we could fix all rc service scripts in base to be compatible w= ith rc_fast_and_loose, but it feels unreasonable. Firstly, this is going to be = an up hill battle in the ports tree. Secondly, being compatible with rc_fast_and_loose requires rc service scripts to use unusual idioms like `(= exit 1)` to set the return code without actually exiting if sourced. My recommendation is to remove support for rc_fast_and_loose. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-282255-20181-1PExRJlhPM>