1 .\" $OpenBSD: zic.8,v 1.4 1997/01/14 03:16:57 millert Exp $
4 zic \- time zone compiler
35 \\$3\*(lq\\$1\*(rq\\$2
38 reads text from the file(s) named on the command line
39 and creates the time conversion information files specified in this input.
44 the standard input is read.
46 These options are available:
49 Create time conversion information files in the named directory rather than
50 in the standard directory named below.
53 Use the given time zone as local time.
55 will act as if the input contained a link line of the form
58 Link \fItimezone\fP localtime
61 Use the given time zone's rules when handling POSIX-format
62 time zone environment variables.
64 will act as if the input contained a link line of the form
67 Link \fItimezone\fP posixrules
69 .BI "\-L " leapsecondfilename
70 Read leap second information from the file with the given name.
71 If this option is not used,
72 no leap second information appears in output files.
75 Complain if a year that appears in a data file is outside the range
76 of years representable by
81 Limit time values stored in output files to values that are the same
82 whether they're taken to be signed or unsigned.
83 You can use this option to generate SVVS-compatible files.
90 when checking year types (see below).
92 Input lines are made up of fields.
93 Fields are separated from one another by any number of white space characters.
94 Leading and trailing white space on input lines is ignored.
95 An unquoted sharp character (#) in the input introduces a comment which extends
96 to the end of the line the sharp character appears on.
97 White space characters and sharp characters may be enclosed in double quotes
98 (") if they're to be used as part of a field.
99 Any line that is blank (after comment stripping) is ignored.
100 Non-blank lines are expected to be of one of three types:
101 rule lines, zone lines, and link lines.
103 A rule line has the form
106 .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
108 Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S
113 Rule US 1967 1973 \- Apr lastSun 2:00 1:00 D
116 The fields that make up a rule line are:
119 Gives the (arbitrary) name of the set of rules this rule is part of.
122 Gives the first year in which the rule applies.
123 Any integer year can be supplied; the Gregorian calendar is assumed.
126 (or an abbreviation) means the minimum year representable as an integer.
129 (or an abbreviation) means the maximum year representable as an integer.
130 Rules can describe times that are not representable as time values,
131 with the unrepresentable times ignored; this allows rules to be portable
132 among hosts with differing time value types.
135 Gives the final year in which the rule applies.
144 may be used to repeat the value of the
149 Gives the type of year in which the rule applies.
154 then the rule applies in all years between
161 is something else, then
165 \fByearistype\fP \fIyear\fP \fItype\fP
167 to check the type of a year:
168 an exit status of zero is taken to mean that the year is of the given type;
169 an exit status of one is taken to mean that the year is not of the given type.
172 Names the month in which the rule takes effect.
173 Month names may be abbreviated.
176 Gives the day on which the rule takes effect.
177 Recognized forms include:
182 5 the fifth of the month
183 lastSun the last Sunday in the month
184 lastMon the last Monday in the month
185 Sun>=8 first Sunday on or after the eighth
186 Sun<=25 last Sunday on or before the 25th
190 Names of days of the week may be abbreviated or spelled out in full.
191 Note that there must be no spaces within the
196 Gives the time of day at which the rule takes effect.
197 Recognized forms include:
203 2:00 time in hours and minutes
204 15:00 24-hour format time (for times after noon)
205 1:28:14 time in hours, minutes, and seconds
209 Any of these forms may be followed by the letter
211 if the given time is local
215 if the given time is local
223 if the given time is universal time;
224 in the absence of an indicator,
225 wall clock time is assumed.
228 Gives 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).
250 of time zone abbreviations to be used when this rule is in effect.
253 the variable part is null.
255 A zone line has the form
259 .ta \w'Zone\0\0'u +\w'Australia/Adelaide\0\0'u +\w'GMTOFF\0\0'u +\w'RULES/SAVE\0\0'u +\w'FORMAT\0\0'u
260 Zone NAME GMTOFF RULES/SAVE FORMAT [UNTIL]
265 Zone Australia/Adelaide 9:30 Aus CST 1971 Oct 31 2:00
268 The fields that make up a zone line are:
271 The name of the time zone.
272 This is the name used in creating the time conversion information file for the
276 The amount of time to add to GMT to get standard time in this zone.
277 This field has the same format as the
281 fields of rule lines;
282 begin the field with a minus sign if time must be subtracted from GMT.
285 The name of the rule(s) that apply in the time zone or,
286 alternately, an amount of time to add to local standard time.
289 then standard time always applies in the time zone.
292 The format for time zone abbreviations in this time zone.
293 The pair of characters
295 is used to show where the
297 of the time zone abbreviation goes.
300 separates standard and daylight abbreviations.
303 The time at which the GMT offset or the rule(s) change for a location.
304 It is specified as a year, a month, a day, and a time of day.
305 If this is specified,
306 the time zone information is generated from the given GMT offset
307 and rule change until the time specified.
308 The month, day, and time of day have the same format as the IN, ON, and AT
309 columns of a rule; trailing columns can be omitted, and default to the
310 earliest possible value for the missing columns.
312 The next line must be a
314 line; this has the same form as a zone line except that the
317 and the name are omitted, as the continuation line will
318 place information starting at the time specified as the
320 field in the previous line in the file used by the previous line.
321 Continuation lines may contain an
323 field, just as zone lines do, indicating that the next line is a further
326 A link line has the form
330 .ta \w'Link\0\0'u +\w'Europe/Istanbul\0\0'u
331 Link LINK-FROM LINK-TO
336 Link Europe/Istanbul Asia/Istanbul
341 field should appear as the
343 field in some zone line;
346 field is used as an alternate name for that zone.
348 Except for continuation lines,
349 lines may appear in any order in the input.
351 Lines in the file that describes leap seconds have the following form:
354 .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
356 Leap YEAR MONTH DAY HH:MM:SS CORR R/S
361 Leap 1974 Dec 31 23:59:60 + S
370 fields tell when the leap second happened.
376 if a second was added
379 if a second was skipped.
380 .\" There's no need to document the following, since it's impossible for more
381 .\" than one leap second to be inserted or deleted at a time.
382 .\" The C Standard is in error in suggesting the possibility.
383 .\" See Terry J Quinn, The BIPM and the accurate measure of time,
384 .\" Proc IEEE 79, 7 (July 1991), 894-905.
387 .\" if two seconds were added
390 .\" if two seconds were skipped.
394 should be (an abbreviation of)
396 if the leap second time given by the other fields should be interpreted as GMT
400 if the leap second time given by the other fields should be interpreted as
401 local wall clock time.
403 For areas with more than two types of local time,
404 you may need to use local standard time in the
406 field of the earliest transition time's rule to ensure that
407 the earliest transition time recorded in the compiled file is correct.
409 /usr/share/zoneinfo standard directory used for created files
411 ctime(3), tzfile(5), zdump(8)
projects / apple / system_cmds.git / blob