1 .\" %%%LICENSE_START(PUBLIC_DOMAIN)
2 .\" This page is in the public domain
5 .TH ZIC 8 2010-02-25 "" "Linux System Administration"
7 zic \- timezone compiler
38 \\$3\*(lq\\$1\*(rq\\$2
41 reads text from the file(s) named on the command line
42 and creates the time conversion information files specified in this input.
47 the standard input is read.
49 These options are available:
52 Create time conversion information files in the named directory rather than
53 in the standard directory named below.
56 Use the given timezone as local time.
58 will act as if the input contained a link line of the form
61 Link \fItimezone\fP localtime
64 Use the given timezone's rules when handling POSIX-format
65 timezone environment variables.
67 will act as if the input contained a link line of the form
70 Link \fItimezone\fP posixrules
72 .BI "\-L " leapsecondfilename
73 Read leap second information from the file with the given name.
74 If this option is not used,
75 no leap second information appears in output files.
78 Complain if a year that appears in a data file is outside the range
79 of years representable by
84 Limit time values stored in output files to values that are the same
85 whether they're taken to be signed or unsigned.
86 You can use this option to generate SVVS-compatible files.
93 when checking year types (see below).
95 Input lines are made up of fields.
96 Fields are separated from one another by any number of white space characters.
97 Leading and trailing white space on input lines is ignored.
98 An unquoted sharp character (#) in the input introduces a comment which extends
99 to the end of the line the sharp character appears on.
100 White space characters and sharp characters may be enclosed in double quotes
101 (") if they're to be used as part of a field.
102 Any line that is blank (after comment stripping) is ignored.
103 Nonblank lines are expected to be of one of three types:
104 rule lines, zone lines, and link lines.
106 A rule line has the form
109 .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
111 Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S
116 Rule US 1967 1973 \- Apr lastSun 2:00 1:00 D
119 The fields that make up a rule line are:
122 Gives the (arbitrary) name of the set of rules this rule is part of.
125 Gives 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.
138 Gives the final year in which the rule applies.
147 may be used to repeat the value of the
152 Gives the type of year in which the rule applies.
157 then the rule applies in all years between
164 is something else, then
172 to check the type of a year:
173 an exit status of zero is taken to mean that the year is of the given type;
174 an exit status of one is taken to mean that the year is not of the given type.
177 Names the month in which the rule takes effect.
178 Month names may be abbreviated.
181 Gives the day on which the rule takes effect.
182 Recognized forms include:
187 5 the fifth of the month
188 lastSun the last Sunday in the month
189 lastMon the last Monday in the month
190 Sun>=8 first Sunday on or after the eighth
191 Sun<=25 last Sunday on or before the 25th
195 Names of days of the week may be abbreviated or spelled out in full.
196 Note that there must be no spaces within the
201 Gives the time of day at which the rule takes effect.
202 Recognized forms include:
208 2:00 time in hours and minutes
209 15:00 24-hour format time (for times after noon)
210 1:28:14 time in hours, minutes, and seconds
215 where hour 0 is midnight at the start of the day,
216 and hour 24 is midnight at the end of the day.
217 Any of these forms may be followed by the letter
219 if the given time is local
223 if the given time is local
231 if the given time is universal time;
232 in the absence of an indicator,
233 wall clock time is assumed.
236 Gives the amount of time to be added to local standard time when the rule is in
238 This field has the same format as the
241 (although, of course, the
245 suffixes are not used).
258 of timezone abbreviations to be used when this rule is in effect.
261 the variable part is null.
263 A zone line has the form
267 .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
268 Zone NAME UTCOFF RULES/SAVE FORMAT [UNTIL]
273 Zone Australia/Adelaide 9:30 Aus CST 1971 Oct 31 2:00
276 The fields that make up a zone line are:
279 The name of the timezone.
280 This is the name used in creating the time conversion information file for the
284 The amount of time to add to UTC to get standard time in this zone.
285 This field has the same format as the
289 fields of rule lines;
290 begin the field with a minus sign if time must be subtracted from UTC.
293 The name of the rule(s) that apply in the timezone or,
294 alternately, an amount of time to add to local standard time.
297 then standard time always applies in the timezone.
300 The format for timezone abbreviations in this timezone.
301 The pair of characters
303 is used to show where the
305 of the timezone abbreviation goes.
308 separates standard and daylight abbreviations.
311 The time at which the UTC offset or the rule(s) change for a location.
312 It is specified as a year, a month, a day, and a time of day.
313 If this is specified,
314 the timezone information is generated from the given UTC offset
315 and rule change until the time specified.
316 The month, day, and time of day have the same format as the IN, ON, and AT
317 columns of a rule; trailing columns can be omitted, and default to the
318 earliest possible value for the missing columns.
320 The next line must be a
322 line; this has the same form as a zone line except that the
325 and the name are omitted, as the continuation line will
326 place information starting at the time specified as the
328 field in the previous line in the file used by the previous line.
329 Continuation lines may contain an
331 field, just as zone lines do, indicating that the next line is a further
334 A link line has the form
338 .ta \w'Link\0\0'u +\w'Europe/Istanbul\0\0'u
339 Link LINK-FROM LINK-TO
344 Link Europe/Istanbul Asia/Istanbul
349 field should appear as the
351 field in some zone line;
354 field is used as an alternate name for that zone.
356 Except for continuation lines,
357 lines may appear in any order in the input.
359 Lines in the file that describes leap seconds have the following form:
362 .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
364 Leap YEAR MONTH DAY HH:MM:SS CORR R/S
369 Leap 1974 Dec 31 23:59:60 + S
378 fields tell when the leap second happened.
384 if a second was added
387 if a second was skipped.
388 .\" There's no need to document the following, since it's impossible for more
389 .\" than one leap second to be inserted or deleted at a time.
390 .\" The C Standard is in error in suggesting the possibility.
391 .\" See Terry J Quinn, The BIPM and the accurate measure of time,
392 .\" Proc IEEE 79, 7 (July 1991), 894-905.
395 .\" if two seconds were added
398 .\" if two seconds were skipped.
402 should be (an abbreviation of)
404 if the leap second time given by the other fields should be interpreted as UTC
408 if the leap second time given by the other fields should be interpreted as
409 local wall clock time.
411 /usr/local/etc/zoneinfo standard directory used for created files
413 For areas with more than two types of local time,
414 you may need to use local standard time in the
416 field of the earliest transition time's rule to ensure that
417 the earliest transition time recorded in the compiled file is correct.
OSDN Git Service
