Precision 380N looses time even with ntpd running using BIOS A06

Matt Wette matt.wette at earthlink.net
Mon Nov 20 08:09:31 CST 2006


Here is your ntp.conf file, with comments cleaned out.

========================================================
restrict 127.0.0.1

server mytrustedtimeserverip
server  10.1.0.248 iburst
server  10.1.0.247 iburst
server  10.0.0.204 iburst

fudge   127.127.1.0 stratum 10
driftfile /var/lib/ntp/drift
broadcastdelay  0.008
authenticate yes
keys            /etc/ntp/keys
==========================================================

You are not using your local clock.  Do you want to add a
line "server 127.127.1.0" ?

You could try starting ntpd with "-d" (multiple times)
to provide some debugging output.  Also, you might try
reducing the number of (external) servers.

The documentation for ntp.conf is pretty bad.  When I
worked on this years ago there were better man pages
around.


Boudreau, Jerry wrote:
> If anyone had any suggestions, I'm having problems with a Precision 380n 
> running:
>  
> Linux flexwks02 2.4.21-27.ELsmp #1 SMP Wed Dec 1 21:59:02 EST 2004 i686 
> i686 i386 GNU/Linux
>  
> I've set it up to syncronize with Windows 2000 A/D servers. The 
> workstation looses syncronization; what am I doing wrong?
>  
>  
> Here is my ntp.conf file:
> -----------------------------------------------------------------------------------------------------------------------------------
> # Prohibit general access to this service.
> #restrict default ignore
> #restrict 192.168.28.130 mask 255.255.255.255 nomodify notrap noquery
>  
> # Permit all access over the loopback interface.  This could # be 
> tightened as well, but to do so would effect some of # the 
> administrative functions.
> restrict 127.0.0.1
>  
> 
> # -- CLIENT NETWORK -------
> # Permit systems on this network to synchronize with this # time 
> service.  Do no
> t permit those systems to modify the # configuration of this service.  
> Also, do
> not use those # systems as peers for synchronization.
> # restrict 192.168.1.0 mask 255.255.255.0 notrust nomodify notrap
>  
> 
> # --- OUR TIMESERVERS -----
> # or remove the default restrict line
> # Permit time synchronization with our time source, but do not # permit 
> the sour
> ce to query or modify the service on this system.
>  
> # restrict mytrustedtimeserverip mask 255.255.255.255 nomodify notrap 
> noquery #
> server mytrustedtimeserverip
>  
>  
>  
> # --- NTP MULTICASTCLIENT ---
> #multicastclient                        # listen on default 224.0.1.1
> # restrict 224.0.1.1 mask 255.255.255.255 notrust nomodify notrap # 
> restrict 192
> .168.1.0 mask 255.255.255.0 notrust nomodify notrap
>  
>  
>  
> # --- GENERAL CONFIGURATION ---
>  
> # Undisciplined Local Clock. This is a fake driver intended for backup # 
> and whe
> n no outside source of synchronized time is available. The # default 
> stratum is
> usually 3, but in this case we elect to use stratum # 0. Since the 
> server line d
> oes not have the prefer keyword, this driver # is never used for 
> synchronization
> , unless no other other # synchronization source is available. In case 
> the local
>  host is # controlled by some external source, such as an external 
> oscillator or
>  # another protocol, the prefer keyword would cause the local host to # 
> disregar
> d all other synchronization sources, unless the kernel # modifications 
> are in us
> e and declare an unsynchronized condition.
> #
> server  10.1.0.248 iburst
> server  10.1.0.247 iburst
> server  10.0.0.204 iburst
> fudge   127.127.1.0 stratum 10
>  
> #
> # Drift file.  Put this in a directory which the daemon can write to.
> # No symbolic links allowed, either, since the daemon updates the file # 
> by crea
> ting a temporary in the same directory and then rename()'ing # it to the 
> file.
> #
> driftfile /var/lib/ntp/drift
> broadcastdelay  0.008
>  
> #
> # Authentication delay.  If you use, or plan to use someday, the # 
> authenticatio
> n facility you should make the programs in the auth_stuff # directory 
> and figure
>  out what this number should be on your machine.
> #
> authenticate yes
>  
> #
> # Keys file.  If you want to diddle your server at run time, make a # 
> keys file
> (mode 600 for sure) and define the key number to be # used for making 
> requests.
> #
> # PLEASE DO NOT USE THE DEFAULT VALUES HERE. Pick your own, or remote # 
> systems
> might be able to reset your clock at will. Note also that # ntpd is 
> started with
>  a -A flag, disabling authentication, that # will have to be removed as 
> well.
> #
> keys            /etc/ntp/keys
>  
>  
>  
> I get the following errors in the log:
>  
> Nov 16 17:58:29 flexwks02 ntpd[6888]: ntpd 4.1.2 at 1.892 
> <mailto:4.1.2 at 1.892> Tue Feb 24 06:32:25 EST 2004 (1)
> Nov 16 17:58:29 flexwks02 ntpd[6888]: precision = 12 usec
> Nov 16 17:58:29 flexwks02 ntpd[6888]: kernel time discipline status 0040
> Nov 16 17:58:29 flexwks02 ntpd[6888]: frequency initialized 1.263 from 
> /var/lib/ntp/drift
> Nov 16 17:58:29 flexwks02 ntpd: ntpd startup succeeded
> Nov 16 17:59:07 flexwks02 ntpd[6888]: kernel time discipline status 
> change 41
> Nov 16 18:00:10 flexwks02 ntpd[6888]: kernel time discipline status change 1
> Nov 16 18:59:59 flexwks02 ntpd[6888]: synchronisation lost
>  
>  
> Any help or suggestions would be appreciated.
>  
> jerry
>  
> 
> 
> 
>  
>  
> 
>  
> 
> ******
> Electronic mail may not be secure and could be intercepted by a third-party.
> Avoid sending confidential or proprietary information, or identifying 
> information
> such as account or social security numbers to others. Further, please do 
> not send
> time-sensitive, action-oriented messages such as orders to buy or sell 
> securities,
> fund transfer instructions, etc., unless authorized by us in writing. 
> Confirmations
> and account statements delivered by U.S. mail are the official records 
> of your account.
> Leerink Swann reserves and intends to exercise the right to review, 
> monitor and retain
> the content of all e-mail communications. Any factual information 
> pertaining to
> publicly-traded securities that is contained herein has been obtained 
> from sources
> believed to be reliable, but we do not guarantee its accuracy or 
> completeness. To
> the extent any investment, economic or other quantifiable performance is 
> referenced
> herein please note that past performance does not guarantee future results.
> 
> -------------------------------------------------
> Leerink Swann & Company
> -------------------------------------------------
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Linux-Desktops mailing list
> Linux-Desktops at dell.com
> http://lists.us.dell.com/mailman/listinfo/linux-desktops
> Please read the FAQ at http://lists.us.dell.com/faq



More information about the Linux-Desktops mailing list