1 .\" $FreeBSD: src/usr.sbin/zic/zic.8,v 1.17 2004/07/02 23:13:00 ru Exp $
14 .Op Fl L Ar leapsecondfilename
17 .Op Fl p Ar posixrules
24 utility reads text from the file(s) named on the command line
25 and creates the time conversion information files specified in this input.
30 the standard input is read.
32 The following options are available:
33 .Bl -tag -width indent
35 Output version information and exit.
37 Do not automatically create directories.
38 If the input file(s) specify
39 an output file in a directory which does not already exist, the
40 default behavior is to attempt to create the directory.
45 will instead error out immediately.
47 Create time conversion information files in the named directory rather than
48 in the standard directory named below.
50 After creating each output file, change its group ownership to the
53 (which can be either a name or a numeric group ID).
54 .It Fl L Ar leapsecondfilename
55 Read leap second information from the file with the given name.
56 If this option is not used,
57 no leap second information appears in output files.
64 utility will act as if the input contained a link line of the form
65 .Bd -literal -offset indent
66 .No "Link timezone localtime
68 (Note that this action has no effect on
70 since the local time zone is specified in
73 .Pa /usr/share/zoneinfo/localtime . )
75 After creating each output file, change its access mode to
77 Both numeric and alphabetic modes are accepted
83 rules when handling POSIX-format
84 time zone environment variables.
87 utility will act as if the input contained a link line of the form
88 .Bd -literal -offset indent
89 .No "Link timezone posixrules
92 After creating each output file, change its owner to
94 (which can be either a name or a numeric user ID).
96 Complain if a year that appears in a data file is outside the range
97 of years representable by
101 Limit time values stored in output files to values that are the same
102 whether they're taken to be signed or unsigned.
103 You can use this option to generate SVVS-compatible files.
109 when checking year types (see below).
112 Input lines are made up of fields.
113 Fields are separated from one another by any number of white space characters.
114 Leading and trailing white space on input lines is ignored.
115 An unquoted sharp character (#) in the input introduces a comment which extends
116 to the end of the line the sharp character appears on.
117 White space characters and sharp characters may be enclosed in double quotes
118 (") if they're to be used as part of a field.
119 Any line that is blank (after comment stripping) is ignored.
120 Non-blank lines are expected to be of one of three types:
121 rule lines, zone lines, and link lines.
123 A rule line has the form:
124 .Dl "Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S
126 .Dl "Rule US 1967 1973 \- Apr lastSun 2:00 1:00 D
128 The fields that make up a rule line are:
129 .Bl -tag -width "LETTER/S" -offset indent
131 Give the (arbitrary) name of the set of rules this rule is part of.
133 Give the first year in which the rule applies.
134 Any integer year can be supplied; the Gregorian calendar is assumed.
137 (or an abbreviation) means the minimum year representable as an integer.
140 (or an abbreviation) means the maximum year representable as an integer.
141 Rules can describe times that are not representable as time values,
142 with the unrepresentable times ignored; this allows rules to be portable
143 among hosts with differing time value types.
145 Give the final year in which the rule applies.
154 may be used to repeat the value of the
158 Give the type of year in which the rule applies.
163 then the rule applies in all years between
170 is something else, then
173 .Li yearistype Ar year Ar type
174 to check the type of a year:
175 an exit status of zero is taken to mean that the year is of the given type;
176 an exit status of one is taken to mean that the year is not of the given type.
178 Name the month in which the rule takes effect.
179 Month names may be abbreviated.
181 Give the day on which the rule takes effect.
182 Recognized forms include:
184 .Bl -tag -width lastSun -compact -offset indent
186 the fifth of the month
188 the last Sunday in the month
190 the last Monday in the month
192 first Sunday on or after the eighth
194 last Sunday on or before the 25th
197 Names of days of the week may be abbreviated or spelled out in full.
198 Note that there must be no spaces within the
202 Give the time of day at which the rule takes effect.
203 Recognized forms include:
205 .Bl -tag -width "\&1:28:14" -offset indent -compact
209 time in hours and minutes
211 24-hour format time (for times after noon)
213 time in hours, minutes, and seconds
216 where hour 0 is midnight at the start of the day,
217 and hour 24 is midnight at the end of the day.
218 Any of these forms may be followed by the letter
220 if the given time is local
224 if the given time is local
232 if the given time is universal time;
233 in the absence of an indicator,
234 wall clock time is assumed.
236 Give 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).
257 of time zone abbreviations to be used when this rule is in effect.
260 the variable part is null.
263 A zone line has the form:
264 .Dl "Zone NAME GMTOFF RULES/SAVE FORMAT [UNTIL]
266 .Dl "Zone Australia/Adelaide 9:30 Aus CST 1971 Oct 31 2:00
267 The fields that make up a zone line are:
268 .Bl -tag -width indent
270 The name of the time zone.
271 This is the name used in creating the time conversion information file for the
274 The amount of time to add to UTC to get standard time in this zone.
275 This field has the same format as the
279 fields of rule lines;
280 begin the field with a minus sign if time must be subtracted from UTC.
282 The name of the rule(s) that apply in the time zone or,
283 alternately, an amount of time to add to local standard time.
286 then standard time always applies in the time zone.
288 The format for time zone abbreviations in this time zone.
289 The pair of characters
291 is used to show where the
293 of the time zone abbreviation goes.
296 separates standard and daylight abbreviations.
298 The time at which the UTC offset or the rule(s) change for a location.
299 It is specified as a year, a month, a day, and a time of day.
300 If this is specified,
301 the time zone information is generated from the given UTC offset
302 and rule change until the time specified.
303 The month, day, and time of day have the same format as the IN, ON, and AT
304 columns of a rule; trailing columns can be omitted, and default to the
305 earliest possible value for the missing columns.
307 The next line must be a
309 line; this has the same form as a zone line except that the
312 and the name are omitted, as the continuation line will
313 place information starting at the time specified as the
315 field in the previous line in the file used by the previous line.
316 Continuation lines may contain an
318 field, just as zone lines do, indicating that the next line is a further
322 A link line has the form
323 .Dl "Link LINK-FROM LINK-TO
325 .Dl "Link Europe/Istanbul Asia/Istanbul
328 field should appear as the
330 field in some zone line;
333 field is used as an alternate name for that zone.
335 Except for continuation lines,
336 lines may appear in any order in the input.
338 Lines in the file that describes leap seconds have the following form:
339 .Dl "Leap YEAR MONTH DAY HH:MM:SS CORR R/S
341 .Dl "Leap 1974 Dec 31 23:59:60 + S
348 fields tell when the leap second happened.
354 if a second was added
357 if a second was skipped.
358 .\" There's no need to document the following, since it's impossible for more
359 .\" than one leap second to be inserted or deleted at a time.
360 .\" The C Standard is in error in suggesting the possibility.
361 .\" See Terry J Quinn, The BIPM and the accurate measure of time,
362 .\" Proc IEEE 79, 7 (July 1991), 894-905.
365 .\" if two seconds were added
368 .\" if two seconds were skipped.
372 should be (an abbreviation of)
374 if the leap second time given by the other fields should be interpreted as UTC
378 if the leap second time given by the other fields should be interpreted as
379 local wall clock time.
381 For areas with more than two types of local time,
382 you may need to use local standard time in the
384 field of the earliest transition time's rule to ensure that
385 the earliest transition time recorded in the compiled file is correct.
387 .Bl -tag -width /usr/share/zoneinfo -compact
388 .It /usr/share/zoneinfo
389 standard directory used for created files