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
36 Do not automatically create directories.
37 If the input file(s) specify
38 an output file in a directory which does not already exist, the
39 default behavior is to attempt to create the directory.
44 will instead error out immediately.
47 Create time conversion information files in the named directory rather than
48 in the standard directory named below.
51 After creating each output file, change its group ownership to the
54 (which can be either a name or a numeric group ID).
56 .It Fl L Ar leapsecondfilename
57 Read leap second information from the file with the given name.
58 If this option is not used,
59 no leap second information appears in output files.
67 utility will act as if the input contained a link line of the form
68 .Bd -literal -offset indent
69 .No "Link timezone localtime
71 (Note that this action has no effect on
73 since the local time zone is specified in
76 .Pa /usr/share/zoneinfo/localtime . )
79 After creating each output file, change its access mode to
81 Both numeric and alphabetic modes are accepted
88 rules when handling POSIX-format
89 time zone environment variables.
92 utility will act as if the input contained a link line of the form
93 .Bd -literal -offset indent
94 .No "Link timezone posixrules
98 Limit time values stored in output files to values that are the same
99 whether they're taken to be signed or unsigned.
100 You can use this option to generate SVVS-compatible files.
103 After creating each output file, change its owner to
105 (which can be either a name or a numeric user ID).
107 Complain if a year that appears in a data file is outside the range
108 of years representable by
113 Output version information and exit.
120 when checking year types (see below).
123 Input lines are made up of fields.
124 Fields are separated from one another by any number of white space characters.
125 Leading and trailing white space on input lines is ignored.
126 An unquoted sharp character (#) in the input introduces a comment which extends
127 to the end of the line the sharp character appears on.
128 White space characters and sharp characters may be enclosed in double quotes
129 (") if they're to be used as part of a field.
130 Any line that is blank (after comment stripping) is ignored.
131 Non-blank lines are expected to be of one of three types:
132 rule lines, zone lines, and link lines.
134 A rule line has the form:
135 .Dl "Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S
137 .Dl "Rule US 1967 1973 \- Apr lastSun 2:00 1:00 D
139 The fields that make up a rule line are:
140 .Bl -tag -width "LETTER/S" -offset indent
142 Give the (arbitrary) name of the set of rules this rule is part of.
144 Give the first year in which the rule applies.
145 Any integer year can be supplied; the Gregorian calendar is assumed.
148 (or an abbreviation) means the minimum year representable as an integer.
151 (or an abbreviation) means the maximum year representable as an integer.
152 Rules can describe times that are not representable as time values,
153 with the unrepresentable times ignored; this allows rules to be portable
154 among hosts with differing time value types.
156 Give the final year in which the rule applies.
165 may be used to repeat the value of the
169 Give the type of year in which the rule applies.
174 then the rule applies in all years between
181 is something else, then
184 .Li yearistype Ar year Ar type
185 to check the type of a year:
186 an exit status of zero is taken to mean that the year is of the given type;
187 an exit status of one is taken to mean that the year is not of the given type.
189 Name the month in which the rule takes effect.
190 Month names may be abbreviated.
192 Give the day on which the rule takes effect.
193 Recognized forms include:
195 .Bl -tag -width lastSun -compact -offset indent
197 the fifth of the month
199 the last Sunday in the month
201 the last Monday in the month
203 first Sunday on or after the eighth
205 last Sunday on or before the 25th
208 Names of days of the week may be abbreviated or spelled out in full.
209 Note that there must be no spaces within the
213 Give the time of day at which the rule takes effect.
214 Recognized forms include:
216 .Bl -tag -width "\&1:28:14" -offset indent -compact
220 time in hours and minutes
222 24-hour format time (for times after noon)
224 time in hours, minutes, and seconds
227 where hour 0 is midnight at the start of the day,
228 and hour 24 is midnight at the end of the day.
229 Any of these forms may be followed by the letter
231 if the given time is local
235 if the given time is local
243 if the given time is universal time;
244 in the absence of an indicator,
245 wall clock time is assumed.
247 Give the amount of time to be added to local standard time when the rule is in
249 This field has the same format as the
252 (although, of course, the
256 suffixes are not used).
268 of time zone abbreviations to be used when this rule is in effect.
271 the variable part is null.
274 A zone line has the form:
275 .Dl "Zone NAME GMTOFF RULES/SAVE FORMAT [UNTIL]
277 .Dl "Zone Australia/Adelaide 9:30 Aus CST 1971 Oct 31 2:00
278 The fields that make up a zone line are:
279 .Bl -tag -width indent
281 The name of the time zone.
282 This is the name used in creating the time conversion information file for the
285 The amount of time to add to UTC to get standard time in this zone.
286 This field has the same format as the
290 fields of rule lines;
291 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 time zone or,
294 alternately, an amount of time to add to local standard time.
297 then standard time always applies in the time zone.
299 The format for time zone abbreviations in this time zone.
300 The pair of characters
302 is used to show where the
304 of the time zone abbreviation goes.
307 separates standard and daylight abbreviations.
309 The time at which the UTC offset or the rule(s) change for a location.
310 It is specified as a year, a month, a day, and a time of day.
311 If this is specified,
312 the time zone information is generated from the given UTC offset
313 and rule change until the time specified.
314 The month, day, and time of day have the same format as the IN, ON, and AT
315 columns of a rule; trailing columns can be omitted, and default to the
316 earliest possible value for the missing columns.
318 The next line must be a
320 line; this has the same form as a zone line except that the
323 and the name are omitted, as the continuation line will
324 place information starting at the time specified as the
326 field in the previous line in the file used by the previous line.
327 Continuation lines may contain an
329 field, just as zone lines do, indicating that the next line is a further
333 A link line has the form
334 .Dl "Link LINK-FROM LINK-TO
336 .Dl "Link Europe/Istanbul Asia/Istanbul
339 field should appear as the
341 field in some zone line;
344 field is used as an alternate name for that zone.
346 Except for continuation lines,
347 lines may appear in any order in the input.
349 Lines in the file that describes leap seconds have the following form:
350 .Dl "Leap YEAR MONTH DAY HH:MM:SS CORR R/S
352 .Dl "Leap 1974 Dec 31 23:59:60 + S
359 fields tell when the leap second happened.
365 if a second was added
368 if a second was skipped.
369 .\" There's no need to document the following, since it's impossible for more
370 .\" than one leap second to be inserted or deleted at a time.
371 .\" The C Standard is in error in suggesting the possibility.
372 .\" See Terry J Quinn, The BIPM and the accurate measure of time,
373 .\" Proc IEEE 79, 7 (July 1991), 894-905.
376 .\" if two seconds were added
379 .\" if two seconds were skipped.
383 should be (an abbreviation of)
385 if the leap second time given by the other fields should be interpreted as UTC
389 if the leap second time given by the other fields should be interpreted as
390 local wall clock time.
392 For areas with more than two types of local time,
393 you may need to use local standard time in the
395 field of the earliest transition time's rule to ensure that
396 the earliest transition time recorded in the compiled file is correct.
398 .Bl -tag -width /usr/share/zoneinfo -compact
399 .It /usr/share/zoneinfo
400 standard directory used for created files
projects / apple / system_cmds.git / blob