1 .\" $FreeBSD: src/usr.sbin/zic/zic.8,v 1.19 2005/02/13 23:45:54 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
66 .D1 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
89 .D1 No "Link timezone posixrules"
91 After creating each output file, change its owner to
93 (which can be either a name or a numeric user ID).
95 Complain if a year that appears in a data file is outside the range
96 of years representable by
100 Limit time values stored in output files to values that are the same
101 whether they are taken to be signed or unsigned.
102 You can use this option to generate SVVS-compatible files.
108 when checking year types (see below).
111 Input lines are made up of fields.
112 Fields are separated from one another by any number of white space characters.
113 Leading and trailing white space on input lines is ignored.
114 An unquoted sharp character (#) in the input introduces a comment which extends
115 to the end of the line the sharp character appears on.
116 White space characters and sharp characters may be enclosed in double quotes
117 (") if they are to be used as part of a field.
118 Any line that is blank (after comment stripping) is ignored.
119 Non-blank lines are expected to be of one of three types:
120 rule lines, zone lines, and link lines.
122 A rule line has the form:
123 .Dl "Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S
125 .Dl "Rule US 1967 1973 \- Apr lastSun 2:00 1:00 D
127 The fields that make up a rule line are:
128 .Bl -tag -width "LETTER/S" -offset indent
130 Give the (arbitrary) name of the set of rules this rule is part of.
132 Give the first year in which the rule applies.
133 Any integer year can be supplied; the Gregorian calendar is assumed.
136 (or an abbreviation) means the minimum year representable as an integer.
139 (or an abbreviation) means the maximum year representable as an integer.
140 Rules can describe times that are not representable as time values,
141 with the unrepresentable times ignored; this allows rules to be portable
142 among hosts with differing time value types.
144 Give the final year in which the rule applies.
153 may be used to repeat the value of the
157 Give the type of year in which the rule applies.
162 then the rule applies in all years between
169 is something else, then
172 .Li yearistype Ar year Ar type
173 to check the type of a year:
174 an exit status of zero is taken to mean that the year is of the given type;
175 an exit status of one is taken to mean that the year is not of the given type.
177 Name the month in which the rule takes effect.
178 Month names may be abbreviated.
180 Give the day on which the rule takes effect.
181 Recognized forms include:
183 .Bl -tag -width lastSun -compact -offset indent
185 the fifth of the month
187 the last Sunday in the month
189 the last Monday in the month
191 first Sunday on or after the eighth
193 last Sunday on or before the 25th
196 Names of days of the week may be abbreviated or spelled out in full.
197 Note that there must be no spaces within the
201 Give the time of day at which the rule takes effect.
202 Recognized forms include:
204 .Bl -tag -width "\&1:28:14" -offset indent -compact
208 time in hours and minutes
210 24-hour format time (for times after noon)
212 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.
235 Give the amount of time to be added to local standard time when the rule is in
237 This field has the same format as the
240 (although, of course, the
244 suffixes are not used).
256 of time zone abbreviations to be used when this rule is in effect.
259 the variable part is null.
262 A zone line has the form:
263 .Dl "Zone NAME GMTOFF RULES/SAVE FORMAT [UNTIL]
265 .Dl "Zone Australia/Adelaide 9:30 Aus CST 1971 Oct 31 2:00
266 The fields that make up a zone line are:
267 .Bl -tag -width indent
269 The name of the time zone.
270 This is the name used in creating the time conversion information file for the
273 The amount of time to add to UTC to get standard time in this zone.
274 This field has the same format as the
278 fields of rule lines;
279 begin the field with a minus sign if time must be subtracted from UTC.
281 The name of the rule(s) that apply in the time zone or,
282 alternately, an amount of time to add to local standard time.
285 then standard time always applies in the time zone.
287 The format for time zone abbreviations in this time zone.
288 The pair of characters
290 is used to show where the
292 of the time zone abbreviation goes.
295 separates standard and daylight abbreviations.
297 The time at which the UTC offset or the rule(s) change for a location.
298 It is specified as a year, a month, a day, and a time of day.
299 If this is specified,
300 the time zone information is generated from the given UTC offset
301 and rule change until the time specified.
302 The month, day, and time of day have the same format as the IN, ON, and AT
303 columns of a rule; trailing columns can be omitted, and default to the
304 earliest possible value for the missing columns.
306 The next line must be a
308 line; this has the same form as a zone line except that the
311 and the name are omitted, as the continuation line will
312 place information starting at the time specified as the
314 field in the previous line in the file used by the previous line.
315 Continuation lines may contain an
317 field, just as zone lines do, indicating that the next line is a further
321 A link line has the form
322 .Dl "Link LINK-FROM LINK-TO
324 .Dl "Link Europe/Istanbul Asia/Istanbul
327 field should appear as the
329 field in some zone line;
332 field is used as an alternate name for that zone.
334 Except for continuation lines,
335 lines may appear in any order in the input.
337 Lines in the file that describes leap seconds have the following form:
338 .Dl "Leap YEAR MONTH DAY HH:MM:SS CORR R/S
340 .Dl "Leap 1974 Dec 31 23:59:60 + S
347 fields tell when the leap second happened.
353 if a second was added
356 if a second was skipped.
357 .\" There's no need to document the following, since it's impossible for more
358 .\" than one leap second to be inserted or deleted at a time.
359 .\" The C Standard is in error in suggesting the possibility.
360 .\" See Terry J Quinn, The BIPM and the accurate measure of time,
361 .\" Proc IEEE 79, 7 (July 1991), 894-905.
364 .\" if two seconds were added
367 .\" if two seconds were skipped.
371 should be (an abbreviation of)
373 if the leap second time given by the other fields should be interpreted as UTC
377 if the leap second time given by the other fields should be interpreted as
378 local wall clock time.
380 For areas with more than two types of local time,
381 you may need to use local standard time in the
383 field of the earliest transition time's rule to ensure that
384 the earliest transition time recorded in the compiled file is correct.
386 .Bl -tag -width /usr/share/zoneinfo -compact
387 .It /usr/share/zoneinfo
388 standard directory used for created files