On some configurations lldpd attempts to create files in chroot. As on BSDs /var/empty is locked for modifications this is not allowed, so I get:
2021-07-22T13:24:21 [CRIT/privsep] unable to create chroot directory: Operation not permitted
The /var/empty exists and is not writable. Using /var/run/lldpd as a chroot works.
Thanks in advance.
- Does the port fail to run in the/with the default configuration?
- What is the minimum configuration required to reproduce the issue?
Well, there are some good questions...
I have two installations on two distinct hosts. And the first works perfectly fine:
FreeBSD limbo.b1t.name 12.2-STABLE FreeBSD 12.2-STABLE r370131 MIN amd64
if_re (driver from ports
The second doesn't:
DragonFly probe2 6.1-DEVELOPMENT DragonFly v22.214.171.1245.g101bb-DEVELOPMENT #5: Wed Jul 28 23:16:28 EEST 2021 arcade@probe2:/usr/obj/usr/src/sys/DMIN x86_64
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 DragonFly. 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.