1 .\" Copyright (c) 1989, 1991, 1993
2 .\" The Regents of the University of California. All rights reserved.
4 .\" This code is derived from software contributed to Berkeley by
7 .\" Redistribution and use in source and binary forms, with or without
8 .\" modification, are permitted provided that the following conditions
10 .\" 1. Redistributions of source code must retain the above copyright
11 .\" notice, this list of conditions and the following disclaimer.
12 .\" 2. Redistributions in binary form must reproduce the above copyright
13 .\" notice, this list of conditions and the following disclaimer in the
14 .\" documentation and/or other materials provided with the distribution.
15 .\" 3. All advertising materials mentioning features or use of this software
16 .\" must display the following acknowledgement:
17 .\" This product includes software developed by the University of
18 .\" California, Berkeley and its contributors.
19 .\" 4. Neither the name of the University nor the names of its contributors
20 .\" may be used to endorse or promote products derived from this software
21 .\" without specific prior written permission.
23 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
24 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
25 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
26 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
27 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
28 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
29 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
30 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
31 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
32 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
35 .\" @(#)tzset.3 8.2 (Berkeley) 11/17/93
36 .\" $FreeBSD: src/lib/libc/gen/tzset.3,v 1.12 2001/10/01 16:08:51 ru Exp $
44 .Nd initialize time conversion information
61 initializes time conversion information used by the library routine
63 The environment variable
65 specifies how this is done.
69 does not appear in the environment, the best available approximation to
70 local wall clock time, as specified by the
71 .Xr tzfile 5 Ns -format
78 appears in the environment but its value is a null string,
79 Coordinated Universal Time
81 is used (without leap second correction).
85 appears in the environment and its value begins with a colon
87 the rest of its value is used as a pathname of a
88 .Xr tzfile 5 Ns -format
89 file from which to read the time conversion information.
90 If the first character of the pathname is a slash
93 an absolute pathname; otherwise, it is used as a pathname relative to
94 the system time conversion information directory.
96 If its value does not begin with a colon, it is first used as the pathname
97 of a file (as described above) from which to read the time conversion
99 If that file cannot be read, the value is then interpreted as a direct
100 specification (the format is described below) of the time conversion
105 environment variable does not specify a
106 .Xr tzfile 5 Ns -format
107 file and cannot be interpreted as a direct specification,
114 sets things up so that
116 returns the best available approximation of local wall clock time.
117 .Sh SPECIFICATION FORMAT
120 is used directly as a specification of the time conversion information,
121 it must have the following syntax (spaces inserted for clarity):
122 .Bd -ragged -offset indent
132 .Bl -tag -width std_and_dst -offset indent
133 .It Em std No and Em dst
134 Three or more bytes that are the designation for the standard
142 is missing, then summer time does not apply in this locale.
143 Upper and lowercase letters are explicitly allowed. Any characters
144 except a leading colon
157 Indicates the value one must add to the local time to arrive at
158 Coordinated Universal Time. The
161 .Bd -ragged -offset indent
174 are optional. The hour
176 is required and may be a single digit. The
184 summer time is assumed to be one hour ahead of standard time. One or
185 more digits may be used; the value is always interpreted as a decimal
186 number. The hour must be between zero and 24, and the minutes (and
187 seconds) \(em if present \(em between zero and 59. If preceded by a
189 the time zone shall be east of the Prime Meridian; otherwise it shall be
190 west (which may be indicated by an optional preceding
193 Indicates when to change to and back from summer time. The
196 .Bd -ragged -offset indent
197 .Em date/time,date/time
202 describes when the change from standard to summer time occurs and the
205 describes when the change back happens. Each
207 field describes when, in current local time, the change to the other
212 is one of the following:
213 .Bl -tag -width "M.m.n.d"
220 Leap days are not counted; that is, in all years \(em including leap
221 years \(em February 28 is day 59 and March 1 is day 60. It is
222 impossible to explicitly refer to the occasional February 29.
224 The zero-based Julian day
228 Leap days are counted, and it is possible to refer to February 29.
253 which may occur in either the fourth or the fifth week). Week 1 is the
254 first week in which the
256 day occurs. Day zero is Sunday.
260 has the same format as
262 except that no leading sign
266 is allowed. The default, if
276 specification, the rules specified
278 .Xr tzfile 5 Ns -format
281 in the system time conversion information directory are used, with the
282 standard and summer time offsets from
284 replaced by those specified by
291 For compatibility with System V Release 3.1, a semicolon
293 may be used to separate the
295 from the rest of the specification.
297 .Bl -tag -width /usr/share/zoneinfo/posixrules -compact
298 .It Pa /etc/localtime
300 .It Pa /usr/share/zoneinfo
302 .It Pa /usr/share/zoneinfo/posixrules
306 .It Pa /usr/share/zoneinfo/GMT
313 .Pa /usr/share/zoneinfo/GMT
316 leap seconds are loaded from
317 .Pa /usr/share/zoneinfo/posixrules .
330 functions first appeared in