OpenQNX :: The QNX Community Portal

 May 13, 2008 - 10:41 AM
Google
  Web openqnx.com   
     Create an account Home · Submit News · QNX Forums · QNX Download · Search   
_
Main Menu
Who's Online
There are 58 unlogged users and 0 registered users online.

You can log-in or register for a user account here.
FAQ FAQ  •  Search Search  •  Register Register  •  Log in to check your private messages Log in to check your private messages
Log in Log in

Time Synchronization with ntpd
OpenQNX Forum Index » QNX Users » QNX6 - Applications
Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Author Message
shilunz
Post subject: Time Synchronization with ntpd  PostPosted: Oct 31, 2007 - 06:58 AM
Active Member


Joined: Sep 07, 2004
Posts: 28
Hi All

I use the ntpd command to synchronize the local time with Windows server, I found no synchronization done.kindly please help for advice.

thanks in advance

Shilunz


# ntpd -d
create_sockets(123)
interface <lo0> OK
ignoring lo0 - not AF_INET
interface <lo0> OK
interface <en0> OK
ignoring en0 - not AF_INET
interface <en0> OK
bind() fd 3, family 2, port 123, addr 0.0.0.0, flags=1
bind() fd 4, family 2, port 123, addr 127.0.0.1, flags=0
bind() fd 5, family 2, port 123, addr 192.168.0.41, flags=1
init_io: maxactivefd 5
peer_clear: at 0 assoc ID 0
newpeer: 192.168.0.41->192.168.0.100 mode 3 vers 4 poll 6 10 flags 281 1 ttl 0 k
ey 00000000
report_event: system event 'event_restart' (0x01) status 'sync_alarm, sync_unspe
c, 1 event, event_unspec' (0xc010)
transmit: at 1 192.168.0.41->192.168.0.100 mode 3
auth_agekeys: at 1 keys 1 expired 0
receive: at 1 192.168.0.41<-192.168.0.100 mode 4 code 1
peer 192.168.0.100 event 'event_reach' (0x84) status 'unreach, conf, 1 event, ev
ent_reach' (0x8014)
clock_filter: n 1 off 638.423131 del 0.000488 dsp 7.945557 jit 0.000488, age 0
transmit: at 16 192.168.0.41->192.168.0.100 mode 3
receive: at 16 192.168.0.41<-192.168.0.100 mode 4 code 1
clock_filter: n 2 off 638.423426 del 0.000488 dsp 3.949641 jit 0.000488, age 0
transmit: at 17 192.168.0.41->192.168.0.100 mode 3
receive: at 17 192.168.0.41<-192.168.0.100 mode 4 code 1
clock_filter: n 2 off 638.423579 del 0.000488 dsp 1.951633 jit 0.000488, age 0
transmit: at 21 192.168.0.41->192.168.0.100 mode 3
receive: at 21 192.168.0.41<-192.168.0.100 mode 4 code 1
clock_filter: n 3 off 638.423191 del 0.000488 dsp 0.952649 jit 0.000488, age 0
transmit: at 25 192.168.0.41->192.168.0.100 mode 3
receive: at 25 192.168.0.41<-192.168.0.100 mode 4 code 1
clock_filter: n 4 off 638.423803 del 0.000488 dsp 0.453159 jit 0.000488, age 0
transmit: at 26 192.168.0.41->192.168.0.100 mode 3
receive: at 26 192.168.0.41<-192.168.0.100 mode 4 code 1
clock_filter: n 5 off 638.423956 del 0.000488 dsp 0.203394 jit 0.000508, age 0
transmit: at 27 192.168.0.41->192.168.0.100 mode 3
receive: at 27 192.168.0.41<-192.168.0.100 mode 4 code 1
clock_filter: n 5 off 638.423109 del 0.000488 dsp 0.078511 jit 0.000597, age 0
transmit: at 28 192.168.0.41->192.168.0.100 mode 3
receive: at 28 192.168.0.41<-192.168.0.100 mode 4 code 1
clock_filter: n 5 off 638.423262 del 0.000488 dsp 0.016069 jit 0.000488, age 0
auth_agekeys: at 60 keys 1 expired 0
transmit: at 93 192.168.0.41->192.168.0.100 mode 3
receive: at 93 192.168.0.41<-192.168.0.100 mode 4 code 1
clock_filter: n 2 off 638.423209 del 0.000488 dsp 0.016543 jit 0.000488, age 0
auth_agekeys: at 120 keys 1 expired 0
transmit: at 158 192.168.0.41->192.168.0.100 mode 3
receive: at 158 192.168.0.41<-192.168.0.100 mode 4 code 1
clock_filter: n 2 off 638.423155 del 0.000488 dsp 0.016778 jit 0.000488, age 0
auth_agekeys: at 180 keys 1 expired 0
transmit: at 224 192.168.0.41->192.168.0.100 mode 3
receive: at 224 192.168.0.41<-192.168.0.100 mode 4 code 1
clock_filter: n 2 off 638.423255 del 0.000488 dsp 0.016901 jit 0.000488, age 0
auth_agekeys: at 240 keys 1 expired 0
transmit: at 290 192.168.0.41->192.168.0.100 mode 3
receive: at 290 192.168.0.41<-192.168.0.100 mode 4 code 1
clock_filter: n 2 off 638.423355 del 0.000488 dsp 0.016961 jit 0.000488, age 0
auth_agekeys: at 300 keys 1 expired 0
transmit: at 356 192.168.0.41->192.168.0.100 mode 3
receive: at 356 192.168.0.41<-192.168.0.100 mode 4 code 1
clock_filter: n 2 off 638.423454 del 0.000488 dsp 0.016989 jit 0.000488, age 0

......
 
 View user's profile Send private message  
Reply with quote Back to top
micro
Post subject: RE: Time Synchronization with ntpd  PostPosted: Oct 31, 2007 - 05:57 PM
Senior Member


Joined: Jul 22, 2004
Posts: 315
Im not quite sure if this is the problem, but we had once trouble synchronizing because the difference between the two workstations was to big.
Also i am not really familiar with the ntpd on QNX, after "synchronizing" manually via date up to 1-2 sec. it suddenly worked for us.
 
 View user's profile Send private message  
Reply with quote Back to top
bishmila
Post subject: RE: Time Synchronization with ntpd  PostPosted: Jan 29, 2008 - 11:51 AM
Active Member


Joined: Dec 12, 2003
Posts: 23
Location: Madrid (Spain)
Are you using the "ntpd" command to synchronize?

As long as I know, the "ntpd" command is used to make your own machine behave as a NTP server.

If you want to synchronize with a remote NTP server just use "ntpdate <NTP Server IP address>". Maybe you need some attempts depending on the
server, but it usually works fine.
 
 View user's profile Send private message  
Reply with quote Back to top
Display posts from previous:     
Jump to:  
All times are GMT
Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
 OpenQNX Forum Index » QNX Users »  QNX6 - Applications
Powered by PNphpBB2 © 2003-2007 The PNphpBB Group
Credits
All logos and trademarks in this site are property of their respective owners. The comments are property of their posters.
Powered by OpenQNX: The QNX Community Portal Site
QNX and the QNX logo are registered trademarks of QNX Software Systems.