Date: Tue, 15 Jan 2019 08:28:22 +0000 From: bugzilla-noreply@freebsd.org To: sysinstall@FreeBSD.org Subject: [Bug 234514] bsdinstall: Stalled after dhclient Message-ID: <bug-234514-8135-y8C9B51cIG@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-234514-8135@https.bugs.freebsd.org/bugzilla/> References: <bug-234514-8135@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=234514 Jason A. Harmening <jah@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jah@FreeBSD.org Assignee|sysinstall@FreeBSD.org |jah@FreeBSD.org --- Comment #1 from Jason A. Harmening <jah@FreeBSD.org> --- It looks like this was caused by r325740 in dhclient. netconfig_ipv4 captures dhclient's stdout using command substitution for possible logging in case dhclient throws an error. The expectation is that this will terminate as soon as dhclient either fails to get a lease and terminates, or succeeds in getting a lease and daemonizes (which closes stdin/stdout/stderr). The switch to cap_syslog broke this behavior, because cap_syslog specifies CASPER_SERVICE_STDIO in its service declaration, so the spawned casper service holds dhclient's stdio descriptors opens. -- 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-234514-8135-y8C9B51cIG>