Lines Matching full:message

131 retransmission when message losses occur.
132 When a message that requires acknowledgment is not acknowledged after
134 the time daemon that has sent the message will assume that the
138 a message type requires a reliable transport mechanism.
140 The message format in TSP is the same for all message types;
142 The next section describes the message format.
144 in detail the different message types, their use and the contents
145 of each field.  NOTE:  The message format is likely to change in
149 Message Format
153 The structure of a TSP message is the following:
155 A one byte message type.
158 message uses.
168 the machine sending the message.
170 The following charts describe the message types,
176 the sending of a message to all active time daemons.
179 Adjtime Message
185 The master sends this message to a slave to communicate
191 This message requires an acknowledgment.
194 Acknowledgment Message
200 Both the master and the slaves use this message for
203 in reply to an Adjtime message.
206 Master Request Message
212 A newly-started time daemon broadcasts this message to
223 The master sends this message to acknowledge the Master Request message
224 and the Conflict Resolution Message.
227 Set Network Time Message
233 The master sends this message to slave time daemons to set their time.
243 Master Active Message
249 The master broadcasts this message to
251 Slaves will reply with a Slave Active message.
254 Slave Active Message
260 A slave sends this message to the master in answer to a Master Active message.
261 This message is also sent when a new slave starts up to inform the master that
265 Master Candidature Message
271 A slave eligible to become a master broadcasts this message when its election
273 The message declares that the slave wishes to become the new master.
276 Candidature Acceptance Message
282 A slave sends this message to accept the candidature of the time daemon
283 that has broadcast an Election message.
288 Candidature Rejection Message
296 with this message.
300 Multiple Master Notification Message
306 When two or more masters reply to a Master Request message, the slave
307 uses this message to inform one of them that more than one master exists.
310 Conflict Resolution Message
317 broadcasts this message to determine who the other masters are.
320 Quit Message
326 This message is sent by the master in three different contexts:
327 1) to a candidate that broadcasts a Master Candidature message,
331 This message requires an acknowledgement.
334 Set Date Message
340 The program \fIdate\fP\|(1) sends this message to the local time daemon
346 Set Date Request Message
352 A slave that has received a Set Date message will communicate the
353 desired date to the master using this message.
356 Set Date Acknowledgment Message
362 The master sends this message to a slave in acknowledgment of a
363 Set Date Request Message.
364 The same message is sent by the local time daemon to the program
369 Start Tracing Message
375 The controlling program \fItimedc\fP sends this message to the local
380 Stop Tracing Message
386 \fITimedc\fP sends this message to the local
391 Master Site Message
397 \fITimedc\fP sends this message to the local time daemon to find out
401 Remote Master Site Message
407 A local time daemon broadcasts this message to find the location
409 It then uses the Acknowledgement message to
413 Test Message
419 For testing purposes, \fItimedc\fP sends this message to a slave
425 Loop Detection Message
453 Postel, J., \fIInternet Control Message Protocol\fP, RFC 792.