Summary: | ntpd configuration files change too much, too often | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Paul Komarek <komarek.paul> |
Component: | Current packages | Assignee: | SpanKY <vapier> |
Status: | RESOLVED WORKSFORME | ||
Severity: | enhancement | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Paul Komarek
2004-03-08 14:38:34 UTC
I must rescind part of my complaint -- the ntp-client initscript still wants its own config file in /etc/conf.d. Unfortunately such a file was not provided during install. Should I feel any happier knowing that ntp-client is supposed to have its own config file? if your system is lacking /etc/conf.d/{ntpd,ntp-client}, that's an issue with portage, not ntp if you dont like using the ntp init scripts, then dont use them ... you obviously have had a lot of trouble with them, so put together your own and forget about it ntp doesnt install it's own /etc/ntp.conf, so i'm not sure what i'm supposed to do about that ntp-client is provided because ntpd confuses a lot of new comers to ntp ... and often times, ntp-client is what new comers want, not ntpd ... ntp technically doesnt have manpages nor will they ever (according to upstream) as for your admin that missed using ntp-client and ntpd, perhaps if you used your own setup rather than the 'Gentoo' one, it wouldnt have happened ? or if he read the man pages as you suggest users should ? i dont see any real issues here if you: (1) have an empty system (2) `emerge ntp` (3a) you want to use ntp-client, edit /etc/conf.d/ntp-client, and add it to the desired runlevel (3b) you want to use ntpd, edit /etc/ntp.conf (creating it after reading the manpages) and /etc/conf.d/ntpd, and add it to the desired runlevel where's the configuration hassle ? I publically apologize for my comment for several reasons: 1) something happened with portage that messed up /etc/conf.d/ntp-client (I'd usually think it was my fault, but I doubt I deleted it manually), and I thought yet-another-ntp-configuration-system had been created 2) even if yet-another-ntp-configuration-system had been created, you don't deserve to be the "verbal victim" of my stress (I'm finishing my thesis and trying to keep our research lab running during weekly air conditioning outages, and I guess I wasn't handling things well that night) 3) it turns out I must have been reading /etc/ntp.conf and thought I was reading /etc/conf.d/ntpd. I had thought that the "new" configuration system (which didn't actually exist) was fiddling with the "restrict" and other directives in /etc/ntp.conf based on the contents of /etc/conf.d/ntpd. Please accept my apologies (that doesn't mean you have to post anything ;-) -Paul Komarek nah, it's ok ... i know the old configuration system (i think pre-4.1.2) was ugly, and i tried a few different things to make it 'nice' ... that led to the 4.1.2 and the system we have now ... i addresses all the known issues and afaik, shouldnt need modification beyond tweaking with unofficial patches (drop-root) ... |