Just trying to brainstorm a few more.... o Interaction / relation with other network time protocols (SNTP? http://www.faqs.org/rfcs/rfc2030.html) o NTP v2-3 authentication (ntp.keys) o As in the config files below: Other security considerations - "restrict" for servers o Multicast mode for subnets - using ntptrace and ntpdc programs (http://www.eecis.udel.edu/~mills/ntp/html/notes.htm) o NTP heirarchies for larger enterprises o The "driftfile" o Differences between various NTP versions (2-4?)
Mark Lachniet [EMAIL PROTECTED] Monika Orski wrote: >If ntp is separated from general time tasks and goes into network services, it could >be something like this: >Set up the system to synchronize the clock over NTP. Configure it to correct clock >drift to match NTP clock. Commands ntpd, ntpdate. Files /etc/ntp.conf, /etc/ntp.drift. > >Did I forget anything? > >:-) >Monika > > >On Tue, 20 November 2001, [EMAIL PROTECTED] wrote: > >> >>Tom has some very good points in this message about including NTP. What >>are your experiences with NTP, and where would NTP be best included? >>Administrative Tasks (objective 1.111) or would this be a network service >>(1.113) ? >> >> -- >>Kara Pritchard Phone: 618-398-7360 >>Director of Exam Development http://www.lpi.org/ >>-- >> >> >>---------- Forwarded message ---------- >>Date: Fri, 17 Aug 2001 23:22:37 +0200 (CEST) >>From: Tom Peters <[EMAIL PROTECTED]> >>Reply-To: [EMAIL PROTECTED] >>To: [EMAIL PROTECTED] >>Cc: [EMAIL PROTECTED] >>Subject: Issue 14: time and clock management >> >>Here is another issue that I would like to see if there is consensus if it >>should be included in L1, and to what extent: >> >>A task from the JAS-2 was delegated for incorporation into L1: >> >>" >>1.2.16 >>none >>Configure ntp.conf and ntp.drift to be used by xntpd >> >> Kara: NTP is not covered currently by Level 1. Move to seed item >> into Level 1 during re-write. >>" >> >>This task pre-supposes that time is properly managed on the system, and >>also that system time actually is regularly corrected using NTP. The >>matter is, that tasks on system clock management have never been included >>in the surveys. IMNSHO this is an important oversight of the surveys, and >>I believe that time management are required tasks for sysadmins. I will >>go so far as to list tasks that I think should go into a L1 >>objective; please let me know what you think, and also how important these >>tasks are in relation to existing test objectives. >> >>- set the hardware (BIOS) clock to the correct date and time >>- set the system date and time >>- configure the correct timezone for the system >>- synchronize the hardware clock and the system time >>- configure the system to regularly synchronize the clock over the >>network using NTP, and configure correction for clock drift >>- Best Practice: maintain the BIOS clock in UTC, configure the timezone >>such that the system time counts local time >>- use commands date, hwclock, ntpdate, ntpd >>- be familar with the timezone database in /usr/share/zoneinfo/ >>- maintain config files /etc/ntp.conf, /etc/ntp.keys, /etc/ntp.drift, >>/etc/timezone, /etc/localtime >> >>-- >> Tom Peters >> Director of the Board & Exam Development Specialist, >> Linux Professional Institute >> e-mail: [EMAIL PROTECTED] >> > >-- >Monika Orski >[EMAIL PROTECTED] >tel 0733 742 773 >www.orski.com > > >-- >This message was sent from the lpi-examdev mailing list. >Send `unsubscribe lpi-examdev' in the subject to [EMAIL PROTECTED] >to leave the list. > -- This message was sent from the lpi-examdev mailing list. Send `unsubscribe lpi-examdev' in the subject to [EMAIL PROTECTED] to leave the list.
