13 .Op Fl L Ar leapsecondfilename
16 .Op Fl p Ar posixrules
22 reads text from the file(s) named on the command line
23 and creates the time conversion information files specified in this input.
28 the standard input is read.
30 The following options are available:
31 .Bl -tag -width indent
33 Do not automatically create directories. If the input file(s) specify
34 an output file in a directory which does not already exist, the
35 default behavior is to attempt to create the directory. If
39 will instead error out immediately.
41 Create time conversion information files in the named directory rather than
42 in the standard directory named below.
44 After creating each output file, change its group ownership to the
47 (which can be either a name or a numeric group ID).
48 .It Fl L Ar leapsecondfilename
49 Read leap second information from the file with the given name.
50 If this option is not used,
51 no leap second information appears in output files.
57 will act as if the input contained a link line of the form
58 .Bd -literal -offset indent
59 .No "Link timezone localtime
61 (Note that this action has no effect on
63 since the local time zone is specified in
66 .Pa /usr/share/zoneinfo/localtime . )
68 After creating each output file, change its access mode to
70 Both numeric and alphabetic modes are accepted
76 rules when handling POSIX-format
77 time zone environment variables.
79 will act as if the input contained a link line of the form
80 .Bd -literal -offset indent
81 .No "Link timezone posixrules
84 After creating each output file, change its owner to
86 (which can be either a name or a numeric user ID).
88 Complain if a year that appears in a data file is outside the range
89 of years representable by
93 Limit time values stored in output files to values that are the same
94 whether they're taken to be signed or unsigned.
95 You can use this option to generate SVVS-compatible files.
101 when checking year types (see below).
104 Input lines are made up of fields.
105 Fields are separated from one another by any number of white space characters.
106 Leading and trailing white space on input lines is ignored.
107 An unquoted sharp character (#) in the input introduces a comment which extends
108 to the end of the line the sharp character appears on.
109 White space characters and sharp characters may be enclosed in double quotes
110 (") if they're to be used as part of a field.
111 Any line that is blank (after comment stripping) is ignored.
112 Non-blank lines are expected to be of one of three types:
113 rule lines, zone lines, and link lines.
115 A rule line has the form:
116 .Dl "Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S
118 .Dl "Rule US 1967 1973 \- Apr lastSun 2:00 1:00 D
120 The fields that make up a rule line are:
121 .Bl -tag -width "LETTER/S" -offset indent
123 Give the (arbitrary) name of the set of rules this rule is part of.
125 Give the first year in which the rule applies.
126 Any integer year can be supplied; the Gregorian calendar is assumed.
129 (or an abbreviation) means the minimum year representable as an integer.
132 (or an abbreviation) means the maximum year representable as an integer.
133 Rules can describe times that are not representable as time values,
134 with the unrepresentable times ignored; this allows rules to be portable
135 among hosts with differing time value types.
137 Give the final year in which the rule applies.
146 may be used to repeat the value of the
150 Give the type of year in which the rule applies.
155 then the rule applies in all years between
162 is something else, then
165 .Li yearistype Ar year Ar type
166 to check the type of a year:
167 an exit status of zero is taken to mean that the year is of the given type;
168 an exit status of one is taken to mean that the year is not of the given type.
170 Name the month in which the rule takes effect.
171 Month names may be abbreviated.
173 Give the day on which the rule takes effect.
174 Recognized forms include:
176 .Bl -tag -width lastSun -compact -offset indent
178 the fifth of the month
180 the last Sunday in the month
182 the last Monday in the month
184 first Sunday on or after the eighth
186 last Sunday on or before the 25th
189 Names of days of the week may be abbreviated or spelled out in full.
190 Note that there must be no spaces within the
194 Give the time of day at which the rule takes effect.
195 Recognized forms include:
197 .Bl -tag -width "\&1:28:14" -offset indent -compact
201 time in hours and minutes
203 24-hour format time (for times after noon)
205 time in hours, minutes, and seconds
208 where hour 0 is midnight at the start of the day,
209 and hour 24 is midnight at the end of the day.
210 Any of these forms may be followed by the letter
212 if the given time is local
216 if the given time is local
224 if the given time is universal time;
225 in the absence of an indicator,
226 wall clock time is assumed.
228 Give the amount of time to be added to local standard time when the rule is in
230 This field has the same format as the
233 (although, of course, the
237 suffixes are not used).
249 of time zone abbreviations to be used when this rule is in effect.
252 the variable part is null.
255 A zone line has the form:
256 .Dl "Zone NAME GMTOFF RULES/SAVE FORMAT [UNTIL]
258 .Dl "Zone Australia/Adelaide 9:30 Aus CST 1971 Oct 31 2:00
259 The fields that make up a zone line are:
260 .Bl -tag -width indent
262 The name of the time zone.
263 This is the name used in creating the time conversion information file for the
266 The amount of time to add to UTC to get standard time in this zone.
267 This field has the same format as the
271 fields of rule lines;
272 begin the field with a minus sign if time must be subtracted from UTC.
274 The name of the rule(s) that apply in the time zone or,
275 alternately, an amount of time to add to local standard time.
278 then standard time always applies in the time zone.
280 The format for time zone abbreviations in this time zone.
281 The pair of characters
283 is used to show where the
285 of the time zone abbreviation goes.
288 separates standard and daylight abbreviations.
290 The time at which the UTC offset or the rule(s) change for a location.
291 It is specified as a year, a month, a day, and a time of day.
292 If this is specified,
293 the time zone information is generated from the given UTC offset
294 and rule change until the time specified.
295 The month, day, and time of day have the same format as the IN, ON, and AT
296 columns of a rule; trailing columns can be omitted, and default to the
297 earliest possible value for the missing columns.
299 The next line must be a
301 line; this has the same form as a zone line except that the
304 and the name are omitted, as the continuation line will
305 place information starting at the time specified as the
307 field in the previous line in the file used by the previous line.
308 Continuation lines may contain an
310 field, just as zone lines do, indicating that the next line is a further
314 A link line has the form
315 .Dl "Link LINK-FROM LINK-TO
317 .Dl "Link Europe/Istanbul Asia/Istanbul
320 field should appear as the
322 field in some zone line;
325 field is used as an alternate name for that zone.
327 Except for continuation lines,
328 lines may appear in any order in the input.
330 Lines in the file that describes leap seconds have the following form:
331 .Dl "Leap YEAR MONTH DAY HH:MM:SS CORR R/S
333 .Dl "Leap 1974 Dec 31 23:59:60 + S
340 fields tell when the leap second happened.
346 if a second was added
349 if a second was skipped.
350 .\" There's no need to document the following, since it's impossible for more
351 .\" than one leap second to be inserted or deleted at a time.
352 .\" The C Standard is in error in suggesting the possibility.
353 .\" See Terry J Quinn, The BIPM and the accurate measure of time,
354 .\" Proc IEEE 79, 7 (July 1991), 894-905.
357 .\" if two seconds were added
360 .\" if two seconds were skipped.
364 should be (an abbreviation of)
366 if the leap second time given by the other fields should be interpreted as UTC
370 if the leap second time given by the other fields should be interpreted as
371 local wall clock time.
373 For areas with more than two types of local time,
374 you may need to use local standard time in the
376 field of the earliest transition time's rule to ensure that
377 the earliest transition time recorded in the compiled file is correct.
379 .Bl -tag -width /usr/share/zoneinfo -compact
380 .It /usr/share/zoneinfo
381 standard directory used for created files