since it may be malloc'ed.
* ntpdc/ntpdc.c (sendrequest): Declare pass as const char *, don't
- loose const in cast.
+ lose const in cast.
* ntpq/ntpq.c (sendrequest): Likewise.
* ntpd/ntp_control.c (ctl_getitem): Remove superfluous cast.
u_char cl_type; /* clock type (ntp control) */
Type if clock as in clock status word (ntp control messages) - usually 0
- u_long cl_maxunsync; /* time to trust oscillator after loosing synch
+ u_long cl_maxunsync; /* time to trust oscillator after losing synch
*/
- seconds a clock can be trusted after loosing synchronisation.
+ seconds a clock can be trusted after losing synchronisation.
u_long cl_speed; /* terminal input & output baudrate */
u_long cl_cflag; /* terminal io flags */
*/
while (sk != 0 && sk->keyid <= NTP_MAXKEY) {
/*
- * Don't loose info which keys are trusted.
+ * Don't lose info as to which keys are trusted.
*/
if (sk->flags & KEY_TRUSTED) {
memset(&sk->k, 0, sizeof(sk->k));
*
* If the file was open before keep the previous generation.
* This will cause output to end up in the 'wrong' file,
- * but I think this is still better than loosing output
+ * but I think this is still better than losing output
*
* ignore errors due to missing directories
*/
* On the next minute it steps forward again :-(
* This is typically 16.5uS/S then 3975uS at the 4min re-sync,
* or 9.5uS/S then 3990.5uS at a 7min re-sync,
- * at which point it may loose the "00" second time stamp.
+ * at which point it may lose the "00" second time stamp.
* I assume that the most accurate time is just AFTER the re-sync.
* Hence remember the last cycle interval,
*
/*
* The first thing we do is see if there is an instance->shmem_fname file (still)
* out there from a previous run. If so, we copy it in and use it to initialize
- * shmem (so we won't loose our almanac if we need it).
+ * shmem (so we won't lose our almanac if we need it).
*/
shmem_old = 0;
int mode;
- /* The M12 with 1.3 or 2.0 Firmware, looses track of all Satellites and has to
- * start again if we go from 0D -> 3D, then looses them again when we
+ /* The M12 with 1.3 or 2.0 Firmware, loses track of all Satellites and has to
+ * start again if we go from 0D -> 3D, then loses them again when we
* go from 3D -> 0D. We do this to get a @@Ea message for SHMEM.
* For NOW we will turn this aspect of filling SHMEM off for the M12
*/
const char *cl_description; /* device name */
const char *cl_format; /* fixed format */
u_char cl_type; /* clock type (ntp control) */
- u_long cl_maxunsync; /* time to trust oscillator after loosing synch */
+ u_long cl_maxunsync; /* time to trust oscillator after losing synch */
u_long cl_speed; /* terminal input & output baudrate */
u_long cl_cflag; /* terminal control flags */
u_long cl_iflag; /* terminal input flags */
"WHARTON 400A Series clock Output Format 1", /* fixed format */
/* Must match a format-name in a libparse/clk_xxx.c file */
DCF_TYPE, /* clock type (ntp control) */
- (1*60*60), /* time to trust oscillator after loosing synch */
+ (1*60*60), /* time to trust oscillator after losing synch */
B9600, /* terminal input & output baudrate */
(CS8|CREAD|PARENB|CLOCAL|HUPCL),/* terminal control flags */
0, /* terminal input flags */
}
/*
- * loose terminal if in daemon operation
+ * lose terminal if in daemon operation
*/
if (!interactive)
detach();