]> git.saurik.com Git - apple/system_cmds.git/blame_incremental - zic.tproj/zic.8
system_cmds-735.50.6.tar.gz
[apple/system_cmds.git] / zic.tproj / zic.8
... / ...
CommitLineData
1.\" $FreeBSD: src/usr.sbin/zic/zic.8,v 1.19 2005/02/13 23:45:54 ru Exp $
2.Dd June 20, 2004
3.Dt ZIC 8
4.Os
5.Sh NAME
6.Nm zic
7.Nd timezone compiler
8.Sh SYNOPSIS
9.Nm
10.Op Fl -version
11.Op Fl Dsv
12.Op Fl d Ar directory
13.Op Fl g Ar group
14.Op Fl L Ar leapsecondfilename
15.Op Fl l Ar localtime
16.Op Fl m Ar mode
17.Op Fl p Ar posixrules
18.Op Fl u Ar user
19.Op Fl y Ar command
20.Op Ar filename ...
21.Sh DESCRIPTION
22The
23.Nm
24utility reads text from the file(s) named on the command line
25and creates the time conversion information files specified in this input.
26If a
27.Ar filename
28is
29.Em - ,
30the standard input is read.
31.Pp
32The following options are available:
33.Bl -tag -width indent
34.It Fl -version
35Output version information and exit.
36.It Fl D
37Do not automatically create directories.
38If the input file(s) specify
39an output file in a directory which does not already exist, the
40default behavior is to attempt to create the directory.
41If
42.Fl D
43is specified,
44.Nm
45will instead error out immediately.
46.It Fl d Ar directory
47Create time conversion information files in the named directory rather than
48in the standard directory named below.
49.It Fl g Ar group
50After creating each output file, change its group ownership to the
51specified
52.Ar group
53(which can be either a name or a numeric group ID).
54.It Fl L Ar leapsecondfilename
55Read leap second information from the file with the given name.
56If this option is not used,
57no leap second information appears in output files.
58.It Fl l Ar timezone
59Use the given
60.Ar time zone
61as local time.
62The
63.Nm
64utility will act as if the input contained a link line of the form
65.Pp
66.D1 No "Link timezone localtime"
67.Pp
68(Note that this action has no effect on
69.Fx ,
70since the local time zone is specified in
71.Pa /etc/localtime
72and not
73.Pa /usr/share/zoneinfo/localtime . )
74.It Fl m Ar mode
75After creating each output file, change its access mode to
76.Ar mode .
77Both numeric and alphabetic modes are accepted
78(see
79.Xr chmod 1 ) .
80.It Fl p Ar timezone
81Use the given
82.Ar "time zone" Ns 's
83rules when handling POSIX-format
84time zone environment variables.
85The
86.Nm
87utility will act as if the input contained a link line of the form
88.Pp
89.D1 No "Link timezone posixrules"
90.It Fl u Ar user
91After creating each output file, change its owner to
92.Ar user
93(which can be either a name or a numeric user ID).
94.It Fl v
95Complain if a year that appears in a data file is outside the range
96of years representable by
97.Xr time 3
98values.
99.It Fl s
100Limit time values stored in output files to values that are the same
101whether they are taken to be signed or unsigned.
102You can use this option to generate SVVS-compatible files.
103.It Fl y Ar command
104Use the given
105.Ar command
106rather than
107.Em yearistype
108when checking year types (see below).
109.El
110.Pp
111Input lines are made up of fields.
112Fields are separated from one another by any number of white space characters.
113Leading and trailing white space on input lines is ignored.
114An unquoted sharp character (#) in the input introduces a comment which extends
115to the end of the line the sharp character appears on.
116White space characters and sharp characters may be enclosed in double quotes
117(") if they are to be used as part of a field.
118Any line that is blank (after comment stripping) is ignored.
119Non-blank lines are expected to be of one of three types:
120rule lines, zone lines, and link lines.
121.Pp
122A rule line has the form:
123.Dl "Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S
124For example:
125.Dl "Rule US 1967 1973 \- Apr lastSun 2:00 1:00 D
126.Pp
127The fields that make up a rule line are:
128.Bl -tag -width "LETTER/S" -offset indent
129.It NAME
130Give the (arbitrary) name of the set of rules this rule is part of.
131.It FROM
132Give the first year in which the rule applies.
133Any integer year can be supplied; the Gregorian calendar is assumed.
134The word
135.Em minimum
136(or an abbreviation) means the minimum year representable as an integer.
137The word
138.Em maximum
139(or an abbreviation) means the maximum year representable as an integer.
140Rules can describe times that are not representable as time values,
141with the unrepresentable times ignored; this allows rules to be portable
142among hosts with differing time value types.
143.It TO
144Give the final year in which the rule applies.
145In addition to
146.Em minimum
147and
148.Em maximum
149(as above),
150the word
151.Em only
152(or an abbreviation)
153may be used to repeat the value of the
154.Em FROM
155field.
156.It TYPE
157Give the type of year in which the rule applies.
158If
159.Em TYPE
160is
161.Em \-
162then the rule applies in all years between
163.Em FROM
164and
165.Em TO
166inclusive.
167If
168.Em TYPE
169is something else, then
170.Nm
171executes the command
172.Li yearistype Ar year Ar type
173to check the type of a year:
174an exit status of zero is taken to mean that the year is of the given type;
175an exit status of one is taken to mean that the year is not of the given type.
176.It IN
177Name the month in which the rule takes effect.
178Month names may be abbreviated.
179.It ON
180Give the day on which the rule takes effect.
181Recognized forms include:
182.Pp
183.Bl -tag -width lastSun -compact -offset indent
184.It \&5
185the fifth of the month
186.It lastSun
187the last Sunday in the month
188.It lastMon
189the last Monday in the month
190.It Sun>=8
191first Sunday on or after the eighth
192.It Sun<=25
193last Sunday on or before the 25th
194.El
195.Pp
196Names of days of the week may be abbreviated or spelled out in full.
197Note that there must be no spaces within the
198.Em ON
199field.
200.It AT
201Give the time of day at which the rule takes effect.
202Recognized forms include:
203.Pp
204.Bl -tag -width "\&1:28:14" -offset indent -compact
205.It 2
206time in hours
207.It 2:00
208time in hours and minutes
209.It 15:00
21024-hour format time (for times after noon)
211.It 1:28:14
212time in hours, minutes, and seconds
213.El
214.Pp
215where hour 0 is midnight at the start of the day,
216and hour 24 is midnight at the end of the day.
217Any of these forms may be followed by the letter
218.Sq Li w
219if the given time is local
220.Dq "wall clock"
221time,
222.Sq Li s
223if the given time is local
224.Dq standard
225time, or
226.Sq Li u
227(or
228.Sq Li g
229or
230.Sq Li z )
231if the given time is universal time;
232in the absence of an indicator,
233wall clock time is assumed.
234.It SAVE
235Give the amount of time to be added to local standard time when the rule is in
236effect.
237This field has the same format as the
238.Em AT
239field
240(although, of course, the
241.Sq Li w
242and
243.Sq Li s
244suffixes are not used).
245.It LETTER/S
246Give the
247.Dq "variable part"
248(for example, the
249.Dq S
250or
251.Dq D
252in
253.Dq EST
254or
255.Dq EDT )
256of time zone abbreviations to be used when this rule is in effect.
257If this field is
258.Em \- ,
259the variable part is null.
260.El
261.Pp
262A zone line has the form:
263.Dl "Zone NAME GMTOFF RULES/SAVE FORMAT [UNTIL]
264For example:
265.Dl "Zone Australia/Adelaide 9:30 Aus CST 1971 Oct 31 2:00
266The fields that make up a zone line are:
267.Bl -tag -width indent
268.It NAME
269The name of the time zone.
270This is the name used in creating the time conversion information file for the
271zone.
272.It GMTOFF
273The amount of time to add to UTC to get standard time in this zone.
274This field has the same format as the
275.Em AT
276and
277.Em SAVE
278fields of rule lines;
279begin the field with a minus sign if time must be subtracted from UTC.
280.It RULES/SAVE
281The name of the rule(s) that apply in the time zone or,
282alternately, an amount of time to add to local standard time.
283If this field is
284.Em \-
285then standard time always applies in the time zone.
286.It FORMAT
287The format for time zone abbreviations in this time zone.
288The pair of characters
289.Em %s
290is used to show where the
291.Dq "variable part"
292of the time zone abbreviation goes.
293Alternately,
294a slash (/)
295separates standard and daylight abbreviations.
296.It UNTIL
297The time at which the UTC offset or the rule(s) change for a location.
298It is specified as a year, a month, a day, and a time of day.
299If this is specified,
300the time zone information is generated from the given UTC offset
301and rule change until the time specified.
302The month, day, and time of day have the same format as the IN, ON, and AT
303columns of a rule; trailing columns can be omitted, and default to the
304earliest possible value for the missing columns.
305.Pp
306The next line must be a
307.Dq continuation
308line; this has the same form as a zone line except that the
309string
310.Dq Zone
311and the name are omitted, as the continuation line will
312place information starting at the time specified as the
313.Em UNTIL
314field in the previous line in the file used by the previous line.
315Continuation lines may contain an
316.Em UNTIL
317field, just as zone lines do, indicating that the next line is a further
318continuation.
319.El
320.Pp
321A link line has the form
322.Dl "Link LINK-FROM LINK-TO
323For example:
324.Dl "Link Europe/Istanbul Asia/Istanbul
325The
326.Em LINK-FROM
327field should appear as the
328.Em NAME
329field in some zone line;
330the
331.Em LINK-TO
332field is used as an alternate name for that zone.
333.Pp
334Except for continuation lines,
335lines may appear in any order in the input.
336.Pp
337Lines in the file that describes leap seconds have the following form:
338.Dl "Leap YEAR MONTH DAY HH:MM:SS CORR R/S
339For example:
340.Dl "Leap 1974 Dec 31 23:59:60 + S
341The
342.Em YEAR ,
343.Em MONTH ,
344.Em DAY ,
345and
346.Em HH:MM:SS
347fields tell when the leap second happened.
348The
349.Em CORR
350field
351should be
352.Dq +
353if a second was added
354or
355.Dq -
356if 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.
362.\" or
363.\" .q ++
364.\" if two seconds were added
365.\" or
366.\" .q --
367.\" if two seconds were skipped.
368The
369.Em R/S
370field
371should be (an abbreviation of)
372.Dq Stationary
373if the leap second time given by the other fields should be interpreted as UTC
374or
375(an abbreviation of)
376.Dq Rolling
377if the leap second time given by the other fields should be interpreted as
378local wall clock time.
379.Sh NOTE
380For areas with more than two types of local time,
381you may need to use local standard time in the
382.Em AT
383field of the earliest transition time's rule to ensure that
384the earliest transition time recorded in the compiled file is correct.
385.Sh FILES
386.Bl -tag -width /usr/share/zoneinfo -compact
387.It /usr/share/zoneinfo
388standard directory used for created files
389.El
390.Sh "SEE ALSO"
391.Xr ctime 3 ,
392.Xr tzfile 5 ,
393.Xr zdump 8
394.\" @(#)zic.8 7.18