Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ut-sally.UUCP
Path: utzoo!decvax!decwrl!pyramid!ut-sally!std-unix
From: std-unix@ut-sally.UUCP (Moderator, John Quarterman)
Newsgroups: mod.std.unix
Subject: Re: TZ and TERM per process
Message-ID: <4029@ut-sally.UUCP>
Date: Wed, 22-Jan-86 17:25:10 EST
Article-I.D.: ut-sally.4029
Posted: Wed Jan 22 17:25:10 1986
Date-Received: Thu, 23-Jan-86 03:23:34 EST
Organization: IEEE/P1003 Portable Operating System Environment Committee
Lines: 28
Approved: jsq@sally.UUCP

[ I don't know if the following suggestion really solves the
problems, but I don't believe anybody has made it before.  -mod ]

From: seismo!philabs!nyit!rick@sally.UTEXAS.EDU (Rick Ace)
Date: Tue, 21 Jan 86 15:51:31 est

Objections to keeping TZ as a UNIX environment object can be
answered by putting the timezone information (to whatever
degree of precision is necessary) in the per-process context
maintained by UNIX, also called the `u.' area.  The kernel
can offer system calls to query or change the TZ of the
calling process.  Upon fork(), the child inherits its
parent's TZ.

The umask(2) syscall provides a precedent for carrying
special OS-related information in the per-process context
maintained by the kernel.  I'm tempted to propose that TERM
information should be kept there too.
-----
Rick Ace
Computer Graphics Laboratory
New York Institute of Technology
Old Westbury, NY  11568
(516) 686-7644

{decvax,seismo}!philabs!nyit!rick

Volume-Number: Volume 0, Number 0