From the openntpd ebuild: ------------------------------ exeinto /etc/init.d newexe ${FILESDIR}/openntpd.rc openntpd insinto /etc/conf.d newins ${FILESDIR}/openntpd.conf.d openntpd ------------------------------ But if you ls -la /usr/portage/net-misc/openntpd/files/ ------------------------------ -rw-r--r-- 1 root root 70 jui 21 01:44 digest-openntpd-20040719p drwxr-xr-x 2 root root 152 jui 21 02:05 ./ drwxr-xr-x 3 root root 176 jui 21 02:05 ../ -rw-r--r-- 1 root root 239 jui 21 01:44 ntpd.conf.d -rwxr-xr-x 1 root root 911 jui 21 01:44 ntpd.rc* ------------------------------ In addition, could someone explain me how to write an init script using openntpd that would sync the machine only at boot and not run the beast as a daemon... ? Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 35889 [details, diff] Quick ebuild patch to fix the conf file paths Simple patch removes the open from the rc files so they get installed correctly. The other option would be to rename the files in the portage tree but I don't know that that matters. As to the above question, I don't know if openntpd has that functionallity. The man page is right out of OpenBSD and there it generally points to using rdate to set your clock the way you describe. The one thing I find confusing is that the man page is ntpd and not openntpd. Aside from the name confusion, what happens when both net-misc/ntp and net-misc/openntpd are emerged? They both have a ntpd man page right? I think that could get very confusing.
AFAIK openntpd currently does not have facilities to sync just once at boot time. I'd suggest you try something like rdate for that or use ntpdate from the vanilla ntpd package.
Thanks, I know about rdate, I was just wondering if this new all-secure daemon had that functionality :)
hmm, i thought i renamed the files before i commited to cvs :/
fixed in cvs, sorry about that
