Hi, does anyone know why NetBSD syslogd implicitly calls chroot, when it was not requested to do so via -t option?
$ syslogd syslogd: Failed to chroot to `/': Operation not permitted syslogd: Fatal error, exiting This prevents syslogd from running as unprivileged user in chroot jail. Is there any security benefit of calling chroot on / directory? I know syslogd can give up root permissions, etc, but I'm playing around with chroot partitions to simulate zones/jails and trying to see how many daemons can be used as unprivileged user.