For some reason, openntpd fails on one of my systems with this error when starting: * Starting ntpd ... fatal: bad privsep dir permissions dispatch_imsg in main: pipe closed Lost child: child exited Terminating I found a workaround here (under Troubleshooting) : http://www.gentoo-wiki.info/HOWTO_NTP_Using_OpenNTPD It appears that /var/lib/openntpd/chroot has to be owned by root for it to be able to function (which is weird, since I have been using it on other systems without problems for a long time).
I already know of bug #108537 , but it seems to still happen on a completly new system.
(In reply to comment #0) > It appears that /var/lib/openntpd/chroot has to be owned by root for it to be > able to function (which is weird, since I have been using it on other systems > without problems for a long time). Confirmed. I've been doing that for at least a couple years on many installs but something tells me it's not the safest thing to do. Denis.
the ebuild installs with the default perms. which is root:root. `stat` shows: File: `/var/tmp/portage/net-misc/openntpd-3.9_p1-r2/image/var/lib/openntpd/chroot' Size: 40 Blocks: 0 IO Block: 4096 directory Device: eh/14d Inode: 145870 Links: 2 Access: (0755/drwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2011-03-05 02:35:38.547667691 -0500 Modify: 2011-03-05 02:35:38.077667691 -0500 Change: 2011-03-05 02:35:38.077667691 -0500 Birth: -
the init.d script now forcibly check things http://sources.gentoo.org/net-misc/openntpd/files/openntpd.rc-3.9_p1-r2?r1=1.2&r2=1.3
Should the check be executed for folder ${NTPD_HOME} instead of hardcoding the /var/lib/openntpd/chroot to the init script as that path can be modified in conf.d/ntpd?
