1 .\" $FreeBSD: src/usr.sbin/zic/zic.8,v 1.11.2.4 2003/03/11 22:31:35 trhodes Exp $
13 .Op Fl L Ar leapsecondfilename
16 .Op Fl p Ar posixrules
23 utility reads text from the file(s) named on the command line
24 and creates the time conversion information files specified in this input.
29 the standard input is read.
31 The following options are available:
32 .Bl -tag -width indent
34 Do not automatically create directories. If the input file(s) specify
35 an output file in a directory which does not already exist, the
36 default behavior is to attempt to create the directory. If
40 will instead error out immediately.
42 Create time conversion information files in the named directory rather than
43 in the standard directory named below.
45 After creating each output file, change its group ownership to the
48 (which can be either a name or a numeric group ID).
49 .It Fl L Ar leapsecondfilename
50 Read leap second information from the file with the given name.
51 If this option is not used,
52 no leap second information appears in output files.
59 utility will act as if the input contained a link line of the form
60 .Bd -literal -offset indent
61 .No "Link timezone localtime
63 (Note that this action has no effect on
65 since the local time zone is specified in
68 .Pa /usr/share/zoneinfo/localtime . )
70 After creating each output file, change its access mode to
72 Both numeric and alphabetic modes are accepted
78 rules when handling POSIX-format
79 time zone environment variables.
82 utility will act as if the input contained a link line of the form
83 .Bd -literal -offset indent
84 .No "Link timezone posixrules
87 After creating each output file, change its owner to
89 (which can be either a name or a numeric user ID).
91 Complain if a year that appears in a data file is outside the range
92 of years representable by
96 Limit time values stored in output files to values that are the same
97 whether they're taken to be signed or unsigned.
98 You can use this option to generate SVVS-compatible files.
104 when checking year types (see below).
107 Input lines are made up of fields.
108 Fields are separated from one another by any number of white space characters.
109 Leading and trailing white space on input lines is ignored.
110 An unquoted sharp character (#) in the input introduces a comment which extends
111 to the end of the line the sharp character appears on.
112 White space characters and sharp characters may be enclosed in double quotes
113 (") if they're to be used as part of a field.
114 Any line that is blank (after comment stripping) is ignored.
115 Non-blank lines are expected to be of one of three types:
116 rule lines, zone lines, and link lines.
118 A rule line has the form:
119 .Dl "Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S
121 .Dl "Rule US 1967 1973 \- Apr lastSun 2:00 1:00 D
123 The fields that make up a rule line are:
124 .Bl -tag -width "LETTER/S" -offset indent
126 Give the (arbitrary) name of the set of rules this rule is part of.
128 Give the first year in which the rule applies.
129 Any integer year can be supplied; the Gregorian calendar is assumed.
132 (or an abbreviation) means the minimum year representable as an integer.
135 (or an abbreviation) means the maximum year representable as an integer.
136 Rules can describe times that are not representable as time values,
137 with the unrepresentable times ignored; this allows rules to be portable
138 among hosts with differing time value types.
140 Give the final year in which the rule applies.
149 may be used to repeat the value of the
153 Give the type of year in which the rule applies.
158 then the rule applies in all years between
165 is something else, then
168 .Li yearistype Ar year Ar type
169 to check the type of a year:
170 an exit status of zero is taken to mean that the year is of the given type;
171 an exit status of one is taken to mean that the year is not of the given type.
173 Name the month in which the rule takes effect.
174 Month names may be abbreviated.
176 Give the day on which the rule takes effect.
177 Recognized forms include:
179 .Bl -tag -width lastSun -compact -offset indent
181 the fifth of the month
183 the last Sunday in the month
185 the last Monday in the month
187 first Sunday on or after the eighth
189 last Sunday on or before the 25th
192 Names of days of the week may be abbreviated or spelled out in full.
193 Note that there must be no spaces within the
197 Give the time of day at which the rule takes effect.
198 Recognized forms include:
200 .Bl -tag -width "\&1:28:14" -offset indent -compact
204 time in hours and minutes
206 24-hour format time (for times after noon)
208 time in hours, minutes, and seconds
211 where hour 0 is midnight at the start of the day,
212 and hour 24 is midnight at the end of the day.
213 Any of these forms may be followed by the letter
215 if the given time is local
219 if the given time is local
227 if the given time is universal time;
228 in the absence of an indicator,
229 wall clock time is assumed.
231 Give the amount of time to be added to local standard time when the rule is in
233 This field has the same format as the
236 (although, of course, the
240 suffixes are not used).
252 of time zone abbreviations to be used when this rule is in effect.
255 the variable part is null.
258 A zone line has the form:
259 .Dl "Zone NAME GMTOFF RULES/SAVE FORMAT [UNTIL]
261 .Dl "Zone Australia/Adelaide 9:30 Aus CST 1971 Oct 31 2:00
262 The fields that make up a zone line are:
263 .Bl -tag -width indent
265 The name of the time zone.
266 This is the name used in creating the time conversion information file for the
269 The amount of time to add to UTC to get standard time in this zone.
270 This field has the same format as the
274 fields of rule lines;
275 begin the field with a minus sign if time must be subtracted from UTC.
277 The name of the rule(s) that apply in the time zone or,
278 alternately, an amount of time to add to local standard time.
281 then standard time always applies in the time zone.
283 The format for time zone abbreviations in this time zone.
284 The pair of characters
286 is used to show where the
288 of the time zone abbreviation goes.
291 separates standard and daylight abbreviations.
293 The time at which the UTC offset or the rule(s) change for a location.
294 It is specified as a year, a month, a day, and a time of day.
295 If this is specified,
296 the time zone information is generated from the given UTC offset
297 and rule change until the time specified.
298 The month, day, and time of day have the same format as the IN, ON, and AT
299 columns of a rule; trailing columns can be omitted, and default to the
300 earliest possible value for the missing columns.
302 The next line must be a
304 line; this has the same form as a zone line except that the
307 and the name are omitted, as the continuation line will
308 place information starting at the time specified as the
310 field in the previous line in the file used by the previous line.
311 Continuation lines may contain an
313 field, just as zone lines do, indicating that the next line is a further
317 A link line has the form
318 .Dl "Link LINK-FROM LINK-TO
320 .Dl "Link Europe/Istanbul Asia/Istanbul
323 field should appear as the
325 field in some zone line;
328 field is used as an alternate name for that zone.
330 Except for continuation lines,
331 lines may appear in any order in the input.
333 Lines in the file that describes leap seconds have the following form:
334 .Dl "Leap YEAR MONTH DAY HH:MM:SS CORR R/S
336 .Dl "Leap 1974 Dec 31 23:59:60 + S
343 fields tell when the leap second happened.
349 if a second was added
352 if a second was skipped.
353 .\" There's no need to document the following, since it's impossible for more
354 .\" than one leap second to be inserted or deleted at a time.
355 .\" The C Standard is in error in suggesting the possibility.
356 .\" See Terry J Quinn, The BIPM and the accurate measure of time,
357 .\" Proc IEEE 79, 7 (July 1991), 894-905.
360 .\" if two seconds were added
363 .\" if two seconds were skipped.
367 should be (an abbreviation of)
369 if the leap second time given by the other fields should be interpreted as UTC
373 if the leap second time given by the other fields should be interpreted as
374 local wall clock time.
376 For areas with more than two types of local time,
377 you may need to use local standard time in the
379 field of the earliest transition time's rule to ensure that
380 the earliest transition time recorded in the compiled file is correct.
382 .Bl -tag -width /usr/share/zoneinfo -compact
383 .It /usr/share/zoneinfo
384 standard directory used for created files