LDP
/
man-pages
mirror of https://github.com/mkerrisk/man-pages
0
1
Fork 0
Code Releases Activity

capget.2, gettimeofday.2, nanosleep.2, process_vm_readv.2, readv.2, seccomp.2, semop.2, sigaction.2, sigwaitinfo.2, dbopen.3, dladdr.3, ether_aton.3, fenv.3, fgetgrent.3, fgetpwent.3, frexp.3, ftime.3, gamma.3, getaddrinfo.3, getaddrinfo_a.3, getgrent_r.3, getgrnam.3, gethostbyname.3, getifaddrs.3, getipnodebyname.3, getmntent.3, getnetent.3, getprotoent.3, getpw.3, getpwent.3, getpwent_r.3, getpwnam.3, getservent.3, getspnam.3, getutent.3, glob.3, hsearch.3, if_nameindex.3, inet.3, mq_receive.3, putgrent.3, putpwent.3, rand.3, sigqueue.3, strfromd.3, strptime.3, strtol.3, termios.3, timeradd.3, lp.4, tty.4, ip.7, ipv6.7, netdevice.7, raw.7, rtnetlink.7, units.7, zic.8: ffix: replace .sp by .PP 

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2017-08-18 01:00:48 +02:00
parent 2dad4c59c8
commit 51f5698d3c
58 changed files with 112 additions and 112 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
man2/capget.2
View File

@ -41,7 +41,7 @@ these system calls (in particular the format of the
.I cap_user_*_t
types) is subject to extension with each kernel revision,
but old programs will keep working.
.sp
.PP
The portable interfaces are
.BR cap_set_proc (3)
and

6
man2/gettimeofday.2
View File

@ -72,7 +72,7 @@ argument is a
.I struct timeval
(as specified in
.IR <sys/time.h> ):
.sp
.PP
.in +4n
.EX
struct timeval {
@ -81,14 +81,14 @@ struct timeval {
};
.EE
.in
.sp
.PP
and gives the number of seconds and microseconds since the Epoch (see
.BR time (2)).
The
.I tz
argument is a
.IR "struct timezone" :
.sp
.PP
.in +4n
.EX
struct timezone {

2
man2/nanosleep.2
View File

@ -76,7 +76,7 @@ The structure
.I timespec
is used to specify intervals of time with nanosecond precision.
It is defined as follows:
.sp
.PP
.in +4n
.nf
struct timespec {

2
man2/process_vm_readv.2
View File

@ -308,7 +308,7 @@ and writes the first 10 bytes into
.I buf1
and the second 10 bytes into
.IR buf2 .
.sp
.PP
.nf
#include <sys/uio.h>

2
man2/readv.2
View File

@ -306,7 +306,7 @@ POSIX.1-2001, POSIX.1-2008,
.BR preadv (),
.BR pwritev ():
nonstandard, but present also on the modern BSDs.
.sp
.PP
.BR preadv2 (),
.BR pwritev2 ():
nonstandard Linux extension.

6
man2/seccomp.2
View File

@ -840,7 +840,7 @@ main(int argc, char **argv)
.BR proc (5),
.BR signal (7),
.BR socket (7)
.sp
.PP
Various pages from the
.I libseccomp
library, including:
@ -850,12 +850,12 @@ library, including:
.BR seccomp_rule_add (3),
and
.BR seccomp_export_bpf (3).
.sp
.PP
The kernel source files
.IR Documentation/networking/filter.txt
and
.IR Documentation/prctl/seccomp_filter.txt .
.sp
.PP
McCanne, S. and Jacobson, V. (1992)
.IR "The BSD Packet Filter: A New Architecture for User-level Packet Capture" ,
Proceedings of the USENIX Winter 1993 Conference

2
man2/semop.2
View File

@ -79,7 +79,7 @@ specifies an operation to be performed on a single semaphore.
The elements of this structure are of type
.IR "struct sembuf" ,
containing the following members:
.sp
.PP
.in +4n
.nf
unsigned short sem_num; /* semaphore number */

4
man2/sigaction.2
View File

@ -98,7 +98,7 @@ is non-NULL, the previous action is saved in
The
.I sigaction
structure is defined as something like:
.sp
.PP
.in +4n
.nf
struct sigaction {
@ -285,7 +285,7 @@ handler(int sig, siginfo_t *info, void *ucontext)
The
.I siginfo_t
data type is a structure with the following fields:
.sp
.PP
.in +4n
.nf
siginfo_t {

4
man2/sigwaitinfo.2
View File

@ -86,7 +86,7 @@ the thread is suspended waiting for a signal.
and kernel scheduling delays mean that the interval
may overrun by a small amount.)
This argument is of the following type:
.sp
.PP
.in +4n
.nf
struct timespec {
@ -95,7 +95,7 @@ struct timespec {
}
.fi
.in
.sp
.PP
If both fields of this structure are specified as 0, a poll is performed:
.BR sigtimedwait ()
returns immediately, either with information about a signal that

2
man3/dbopen.3
View File

@ -151,7 +151,7 @@ structure is defined in the
.I <db.h>
include file, and contains at
least the following fields:
.sp
.PP
.in +4n
.nf
typedef struct {

2
man3/dladdr.3
View File

@ -52,7 +52,7 @@ returns information about the shared object and symbol that overlaps
This information is returned in a
.I Dl_info
structure:
.sp
.PP
.in +4n
.nf
typedef struct {

2
man3/ether_aton.3
View File

@ -116,7 +116,7 @@ The structure
is defined in
.I <net/ethernet.h>
as:
.sp
.PP
.in +4n
.nf
struct ether_addr {

2
man3/fenv.3
View File

@ -320,7 +320,7 @@ to query the state.
.EX
.BR "#define _GNU_SOURCE" " /* See feature_test_macros(7) */"
.B "#include <fenv.h>"
.sp
.PP
.BI "int feenableexcept(int " excepts );
.BI "int fedisableexcept(int " excepts );
.B "int fegetexcept(void);"

2
man3/fgetgrent.3
View File

@ -65,7 +65,7 @@ must have the same format as
.BR group (5)).
.PP
The \fIgroup\fP structure is defined in \fI<grp.h>\fP as follows:
.sp
.PP
.in +4n
.nf
struct group {

2
man3/fgetpwent.3
View File

@ -67,7 +67,7 @@ must have the same format as
.BR passwd (5)).
.PP
The \fIpasswd\fP structure is defined in \fI<pwd.h>\fP as follows:
.sp
.PP
.in +4n
.nf
struct passwd {

2
man3/frexp.3
View File

@ -122,7 +122,7 @@ also conforms to
SVr4, 4.3BSD, C89.
.SH EXAMPLE
The program below produces results such as the following:
.sp
.PP
.nf
.in +4n
.RB "$" " ./a.out 2560"

2
man3/ftime.3
View File

@ -40,7 +40,7 @@ since the Epoch, 1970-01-01 00:00:00 +0000 (UTC).
The time is returned in
.IR tp ,
which is declared as follows:
.sp
.PP
.in +4n
.nf
struct timeb {

4
man3/gamma.3
View File

@ -96,12 +96,12 @@ in the external integer
In 4.3BSD the name was changed to
.BR lgamma (3),
and the man page promises
.sp
.PP
.in +4n
"At some time in the future the name gamma will be rehabilitated
and used for the Gamma function"
.in
.sp
.PP
This did indeed happen in 4.4BSD, where
.BR gamma ()
computes the Gamma function (with no effect on

2
man3/getaddrinfo.3
View File

@ -103,7 +103,7 @@ The
structure used by
.BR getaddrinfo ()
contains the following fields:
.sp
.PP
.in +4n
.nf
struct addrinfo {

2
man3/getaddrinfo_a.3
View File

@ -86,7 +86,7 @@ are ignored.
Each request is described by a
.I gaicb
structure, defined as follows:
.sp
.PP
.in +4n
.nf
struct gaicb {

8
man3/getgrent_r.3
View File

@ -68,7 +68,7 @@ The latter reads the next group entry from
The \fIgroup\fP structure is defined in
.I <grp.h>
as follows:
.sp
.PP
.in +4n
.nf
struct group {
@ -150,16 +150,16 @@ These functions are GNU extensions, done in a style resembling
the POSIX version of functions like
.BR getpwnam_r (3).
Other systems use the prototype
.sp
.PP
.in +4n
.nf
struct group *getgrent_r(struct group *grp, char *buf,
int buflen);
.fi
.in
.sp
.PP
or, better,
.sp
.PP
.in +4n
.nf
int getgrent_r(struct group *grp, char *buf, int buflen,

2
man3/getgrnam.3
View File

@ -83,7 +83,7 @@ that matches the group ID
.IR gid .
.PP
The \fIgroup\fP structure is defined in \fI<grp.h>\fP as follows:
.sp
.PP
.in +4n
.nf
struct group {

2
man3/gethostbyname.3
View File

@ -258,7 +258,7 @@ keyword was used to control the order of host lookups as defined in
.PP
.PP
The \fIhostent\fP structure is defined in \fI<netdb.h>\fP as follows:
.sp
.PP
.in +4n
.nf
struct hostent {

2
man3/getifaddrs.3
View File

@ -55,7 +55,7 @@ and stores the address of the first item of the list in
The list consists of
.I ifaddrs
structures, defined as follows:
.sp
.PP
.in +4n
.nf
struct ifaddrs {

2
man3/getipnodebyname.3
View File

@ -56,7 +56,7 @@ and
functions return the names and addresses of a network host.
These functions return a pointer to the
following structure:
.sp
.PP
.in +4n
.nf
struct hostent {

2
man3/getmntent.3
View File

@ -149,7 +149,7 @@ The
structure is defined in
.I <mntent.h>
as follows:
.sp
.PP
.in +4n
.nf
struct mntent {

2
man3/getnetent.3
View File

@ -99,7 +99,7 @@ The
structure is defined in
.I <netdb.h>
as follows:
.sp
.PP
.in +4n
.nf
struct netent {

2
man3/getprotoent.3
View File

@ -97,7 +97,7 @@ The
structure is defined in
.I <netdb.h>
as follows:
.sp
.PP
.in +4n
.nf
struct protoent {

2
man3/getpw.3
View File

@ -54,7 +54,7 @@ The returned buffer contains a line of format
.in
.PP
The \fIpasswd\fP structure is defined in \fI<pwd.h>\fP as follows:
.sp
.PP
.in +4n
.nf
struct passwd {

2
man3/getpwent.3
View File

@ -85,7 +85,7 @@ function is used to close the password database
after all processing has been performed.
.PP
The \fIpasswd\fP structure is defined in \fI<pwd.h>\fP as follows:
.sp
.PP
.in +4n
.nf
struct passwd {

8
man3/getpwent_r.3
View File

@ -68,7 +68,7 @@ The latter reads the next passwd entry from
The \fIpasswd\fP structure is defined in
.I <pwd.h>
as follows:
.sp
.PP
.in +4n
.nf
struct passwd {
@ -152,16 +152,16 @@ These functions are GNU extensions, done in a style resembling
the POSIX version of functions like
.BR getpwnam_r (3).
Other systems use the prototype
.sp
.PP
.in +4n
.nf
struct passwd *
getpwent_r(struct passwd *pwd, char *buf, int buflen);
.fi
.in
.sp
.PP
or, better,
.sp
.PP
.nf
.in +4n
int

2
man3/getpwnam.3
View File

@ -85,7 +85,7 @@ that matches the user ID
.IR uid .
.PP
The \fIpasswd\fP structure is defined in \fI<pwd.h>\fP as follows:
.sp
.PP
.in +4n
.nf
struct passwd {

2
man3/getservent.3
View File

@ -112,7 +112,7 @@ The
structure is defined in
.I <netdb.h>
as follows:
.sp
.PP
.in +4n
.nf
struct servent {

2
man3/getspnam.3
View File

@ -186,7 +186,7 @@ often with different prototypes.
.\" SUN doesn't have sgetspent_r()
.SS Structure
The shadow password structure is defined in \fI<shadow.h>\fP as follows:
.sp
.PP
.in +4n
.nf
struct spwd {

4
man3/getutent.3
View File

@ -285,7 +285,7 @@ Glibc adds reentrant versions
Feature Test Macro Requirements for glibc (see
.BR feature_test_macros (7)):
.in
.sp
.PP
.BR getutent_r (),
.BR getutid_r (),
.BR getutline_r ():
@ -294,7 +294,7 @@ Feature Test Macro Requirements for glibc (see
|| /* since glibc 2.19: */ _DEFAULT_SOURCE
|| /* glibc <= 2.19: */ _SVID_SOURCE || _BSD_SOURCE
.fi
.sp
.PP
These functions are GNU extensions, analogs of the functions of the
same name without the _r suffix.
The

4
man3/glob.3
View File

@ -331,13 +331,13 @@ These will store their error code in
.IR errno .
.SH EXAMPLE
One example of use is the following code, which simulates typing
.sp
.PP
.in +4n
.EX
ls \-l *.c ../*.c
.EE
.in
.sp
.PP
in the shell:
.nf
.in +4n

4
man3/hsearch.3
View File

@ -126,7 +126,7 @@ and if successful returns a pointer to it.
The argument \fIitem\fP is of type \fIENTRY\fP, which is defined in
\fI<search.h>\fP as follows:
.in +4n
.sp
.PP
.nf
typedef struct entry {
char *key;
@ -134,7 +134,7 @@ typedef struct entry {
} ENTRY;
.in
.fi
.sp
.PP
The field \fIkey\fP points to a null-terminated string which is the
search key.
The field \fIdata\fP points to data that is associated with that key.

2
man3/if_nameindex.3
View File

@ -43,7 +43,7 @@ about one of the network interfaces on the local system.
The
.I if_nameindex
structure contains at least the following entries:
.sp
.PP
.in +4n
.EX
unsigned int if_index; /* Index of interface (1, 2, ...) */

2
man3/inet.3
View File

@ -210,7 +210,7 @@ and
is defined in
.I <netinet/in.h>
as:
.sp
.PP
.in +4n
.EX
typedef uint32_t in_addr_t;

2
man3/mq_receive.3
View File

@ -95,7 +95,7 @@ points to a structure which specifies how long the call will block.
This value is an absolute timeout in seconds and nanoseconds
since the Epoch, 1970-01-01 00:00:00 +0000 (UTC),
specified in the following structure:
.sp
.PP
.in +4n
.nf
struct timespec {

4
man3/putgrent.3
View File

@ -23,11 +23,11 @@ The function writes the content of the provided
into the
.IR stream .
The list of group members must be NULL-terminated or NULL-initialized.
.sp
.PP
The
.IR "struct group"
is defined as follows:
.sp
.PP
.in +4n
.EX
struct group {

2
man3/putpwent.3
View File

@ -56,7 +56,7 @@ function writes a password entry from the
structure \fIp\fP in the file associated with \fIstream\fP.
.PP
The \fIpasswd\fP structure is defined in \fI<pwd.h>\fP as follows:
.sp
.PP
.in +4n
.EX
struct passwd {

2
man3/rand.3
View File

@ -183,7 +183,7 @@ POSIX.1-2001 gives the following example of an implementation of
and
.BR srand (),
possibly useful when one needs the same sequence on two different machines.
.sp
.PP
.in +4n
.EX
static unsigned long next = 1;

2
man3/sigqueue.3
View File

@ -57,7 +57,7 @@ The
.I value
argument is used to specify an accompanying item of data (either an integer
or a pointer value) to be sent with the signal, and has the following type:
.sp
.PP
.in +4n
.EX
union sigval {

22
man3/strfromd.3
View File

@ -70,13 +70,13 @@ At most
.I n
characters are stored into
.IR str .
.sp
.PP
The terminating null character ('\\0') is written if and only if
.I n
is sufficiently large, otherwise the written string is truncated at
.I n
characters.
.sp
.PP
The
.BR strfromd (),
.BR strfromf (),
@ -111,7 +111,7 @@ Finally, the format string should have one of the conversion specifiers
.BR g ,
or
.BR G .
.sp
.PP
The conversion specifier is applied based on the floating-point type
indicated by the function suffix.
Therefore, unlike
@ -120,7 +120,7 @@ the format string does not have a length modifier character.
See
.BR snprintf (3)
for a detailed description of these conversion specifiers.
.sp
.PP
The implementation conforms to the C99 standard on conversion of NaN and
infinity values:
.PP
@ -142,7 +142,7 @@ If
.BR E ,
.BR G )
is the conversion specifier, the conversion is to "NAN" or "-NAN".
.sp
.PP
Likewise if
.I fp
is infinity, it is converted to [-]inf or [-]INF.
@ -179,7 +179,7 @@ For an explanation of the terms used in this section, see
and the
.B POSIX Safety Concepts
section in GNU C Library manual.
.sp
.PP
.TS
allbox;
lbw11 lb lb
@ -209,7 +209,7 @@ category of the current locale.
.SH EXAMPLES
To convert the value 12.1 as a float type to a string using decimal
notation, resulting in "12.100000":
.sp
.PP
.in +4
.EX
#define __STDC_WANT_IEC_60559_BFP_EXT__
@ -219,10 +219,10 @@ char s[ssize];
strfromf(s, ssize, "%f", 12.1);
.EE
.in
.sp
.PP
To convert the value 12.3456 as a float type to a string using
decimal notation with two digits of precision, resulting in "12.35":
.sp
.PP
.in +4
.EX
#define __STDC_WANT_IEC_60559_BFP_EXT__
@ -232,10 +232,10 @@ char s[ssize];
strfromf(s, ssize, "%.2f", 12.3456);
.EE
.in
.sp
.PP
To convert the value 12.345e19 as a double type to a string using
scientific notation with zero digits of precision, resulting in "1E+20":
.sp
.PP
.in +4
.EX
#define __STDC_WANT_IEC_60559_BFP_EXT__

4
man3/strptime.3
View File

@ -57,7 +57,7 @@ The broken-down time structure
is defined in
.IR <time.h>
as follows:
.sp
.PP
.in +4n
.EX
struct tm {
@ -417,7 +417,7 @@ The following example demonstrates the use of
.BR strptime ()
and
.BR strftime (3).
.sp
.PP
.EX
#define _XOPEN_SOURCE
#include <stdio.h>

2
man3/strtol.3
View File

@ -200,7 +200,7 @@ these functions may accept other,
implementation-defined numeric strings.
.LP
BSD also has
.sp
.PP
.in +4n
.EX
.BI "quad_t strtoq(const char *" nptr ", char **" endptr ", int " base );

2
man3/termios.3
View File

@ -92,7 +92,7 @@ provided to control asynchronous communications ports.
Many of the functions described here have a \fItermios_p\fP argument
that is a pointer to a \fItermios\fP structure.
This structure contains at least the following members:
.sp
.PP
.in +4n
.EX
tcflag_t c_iflag; /* input modes */

2
man3/timeradd.3
View File

@ -60,7 +60,7 @@ The macros are provided to operate on
structures, defined in
.I <sys/time.h>
as:
.sp
.PP
.in +4n
.EX
struct timeval {

2
man4/lp.4
View File

@ -117,7 +117,7 @@ LP_POUTPA unchanged out-of-paper input, active high
LP_PSELECD unchanged selected input, active high
LP_PERRORP unchanged error input, active low
.TE
.sp
.PP
Refer to your printer manual for the meaning of the signals.
Note that undocumented bits may also be set, depending on your printer.
.IP "\fBint ioctl(int \fP\fIfd\fP\fB, LPRESET)\fP"

4
man4/tty.4
View File

@ -46,7 +46,7 @@ request
is supported.
.SS TIOCNOTTY
Detach the calling process from its controlling terminal.
.sp
.PP
If the process is the session leader,
then
.B SIGHUP
@ -54,7 +54,7 @@ and
.B SIGCONT
signals are sent to the foreground process group
and all processes in the current session lose their controlling tty.
.sp
.PP
This
.BR ioctl (2)
call works only on file descriptors connected

8
man7/ip.7
View File

@ -314,7 +314,7 @@ from a specified source.
Argument is an
.I ip_mreq_source
structure.
.sp
.PP
.in +4n
.EX
struct ip_mreq_source {
@ -327,7 +327,7 @@ struct ip_mreq_source {
};
.EE
.in
.sp
.PP
The
.I ip_mreq_source
structure is similar to
@ -428,7 +428,7 @@ This option provides access to the advanced full-state filtering API.
Argument is an
.I ip_msfilter
structure.
.sp
.PP
.in +4n
.EX
struct ip_msfilter {
@ -445,7 +445,7 @@ struct ip_msfilter {
};
.EE
.in
.sp
.PP
There are two macros,
.BR MCAST_INCLUDE
and

2
man7/ipv6.7
View File

@ -155,7 +155,7 @@ struct in6_addr {
};
.EE
.in
.sp
.PP
.I sin6_family
is always set to
.BR AF_INET6 ;

4
man7/netdevice.7
View File

@ -140,7 +140,7 @@ IFF_BONDING:Interface is a bonding master or slave.
IFF_SLAVE_NEEDARP:Interface needs ARPs for validation.
IFF_ISATAP:Interface is RFC4214 ISATAP interface.
.TE
.sp
.PP
Setting the extended (private) interface flags is a privileged operation.
.TP
.BR SIOCGIFADDR ", " SIOCSIFADDR
@ -362,7 +362,7 @@ glibc 2.1 is missing the
macro in
.IR <net/if.h> .
Add the following to your program as a workaround:
.sp
.PP
.in +4n
.EX
#ifndef ifr_newname

2
man7/raw.7
View File

@ -66,7 +66,7 @@ Packet ID:Filled in when zero
Total Length:Always filled in
.TE
.RE
.sp
.PP
.PP
If
.B IP_HDRINCL

2
man7/rtnetlink.7
View File

@ -107,7 +107,7 @@ IFLA_STATS:T{
see below
T}:Interface Statistics.
.TE
.sp
.PP
The value type for
.B IFLA_STATS
is

2
man7/units.7
View File

@ -87,7 +87,7 @@ Ei exbi 2^60 = 1152921504606846976
.RE
.PP
See also
.sp
.PP
.UR http://physics.nist.gov\:/cuu\:/Units\:/binary.html
.UE
.SS Discussion

44
man8/zic.8
View File

@ -40,7 +40,7 @@ in the standard directory named below.
Use the given timezone as local time.
.B zic
will act as if the input contained a link line of the form
.sp
.PP
.ti +.5i
Link \fItimezone\fP localtime
.TP
@ -49,7 +49,7 @@ Use the given timezone's rules when handling POSIX-format
timezone environment variables.
.B zic
will act as if the input contained a link line of the form
.sp
.PP
.ti +.5i
Link \fItimezone\fP posixrules
.TP
@ -91,14 +91,14 @@ A rule line has the form
.nf
.ti +.5i
.ta \w'Rule\0\0'u +\w'NAME\0\0'u +\w'FROM\0\0'u +\w'1973\0\0'u +\w'TYPE\0\0'u +\w'Apr\0\0'u +\w'lastSun\0\0'u +\w'2:00\0\0'u +\w'SAVE\0\0'u
.sp
.PP
Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S
.sp
.PP
For example:
.ti +.5i
.sp
.PP
Rule US 1967 1973 \- Apr lastSun 2:00 1:00 D
.sp
.PP
.fi
The fields that make up a rule line are:
.TP "\w'LETTER/S'u"
@ -166,7 +166,7 @@ Gives the day on which the rule takes effect.
Recognized forms include:
.nf
.in +.5i
.sp
.PP
.ta \w'Sun<=25\0\0'u
5 the fifth of the month
lastSun the last Sunday in the month
@ -175,7 +175,7 @@ Sun>=8 first Sunday on or after the eighth
Sun<=25 last Sunday on or before the 25th
.fi
.in -.5i
.sp
.PP
Names of days of the week may be abbreviated or spelled out in full.
Note that there must be no spaces within the
.B ON
@ -186,7 +186,7 @@ Gives the time of day at which the rule takes effect.
Recognized forms include:
.nf
.in +.5i
.sp
.PP
.ta \w'1:28:13\0\0'u
2 time in hours
2:00 time in hours and minutes
@ -195,7 +195,7 @@ Recognized forms include:
\- equivalent to 0
.fi
.in -.5i
.sp
.PP
where hour 0 is midnight at the start of the day,
and hour 24 is midnight at the end of the day.
Any of these forms may be followed by the letter
@ -245,17 +245,17 @@ If this field is
the variable part is null.
.PP
A zone line has the form
.sp
.PP
.nf
.ti +.5i
.ta \w'Zone\0\0'u +\w'Australia/Adelaide\0\0'u +\w'UTCOFF\0\0'u +\w'RULES/SAVE\0\0'u +\w'FORMAT\0\0'u
Zone NAME UTCOFF RULES/SAVE FORMAT [UNTIL]
.sp
.PP
For example:
.sp
.PP
.ti +.5i
Zone Australia/Adelaide 9:30 Aus CST 1971 Oct 31 2:00
.sp
.PP
.fi
The fields that make up a zone line are:
.TP "\w'UTCOFF'u"
@ -316,17 +316,17 @@ field, just as zone lines do, indicating that the next line is a further
continuation.
.PP
A link line has the form
.sp
.PP
.nf
.ti +.5i
.ta \w'Link\0\0'u +\w'Europe/Istanbul\0\0'u
Link LINK-FROM LINK-TO
.sp
.PP
For example:
.sp
.PP
.ti +.5i
Link Europe/Istanbul Asia/Istanbul
.sp
.PP
.fi
The
.B LINK-FROM
@ -344,14 +344,14 @@ Lines in the file that describes leap seconds have the following form:
.nf
.ti +.5i
.ta \w'Leap\0\0'u +\w'YEAR\0\0'u +\w'MONTH\0\0'u +\w'DAY\0\0'u +\w'HH:MM:SS\0\0'u +\w'CORR\0\0'u
.sp
.PP
Leap YEAR MONTH DAY HH:MM:SS CORR R/S
.sp
.PP
For example:
.ti +.5i
.sp
.PP
Leap 1974 Dec 31 23:59:60 + S
.sp
.PP
.fi
The
.BR YEAR ,