Date: Thu, 29 Jul 2021 09:28:20 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 257330] net-mgmt/lldpd: Fails to run in some configurations: CRIT/privsep] unable to create chroot directory: Operation not permitted Message-ID: <bug-257330-7788-QQIEaEdFu2@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-257330-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-257330-7788@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=3D257330 --- Comment #2 from Volodymyr Kostyrko <arcade@b1t.name> --- Well, there are some good questions... I have two installations on two distinct hosts. And the first works perfect= ly fine: FreeBSD limbo.b1t.name 12.2-STABLE FreeBSD 12.2-STABLE r370131 MIN amd64 Interfaces: if_bridge if_ste if_re (driver from ports if_em The second doesn't: DragonFly probe2 6.1-DEVELOPMENT DragonFly v6.1.0.385.g101bb-DEVELOPMENT #5: Wed Jul 28 23:16:28 EEST 2021 arcade@probe2:/usr/obj/usr/src/sys/DMIN=20 x86_64 Interfaces: ath0: AR9220 In both cases default configuration was used, works on first host after install+onestart, doesn't work on second one in same way. All defaults. This might be triggered with something about WiFi or something about Dragon= Fly. I'll try to install FreeBSD on the same host and recheck. I created a ticket just because: 1. Change originated from FreeBSD ports, not DPorts. 2. It looks illogical to use /var/empty for chroot, as you can't even get /= dev in there. But yeah, it's a fair question, I'll try to retest on FreeBSD. --=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-257330-7788-QQIEaEdFu2>