home *** CD-ROM | disk | FTP | other *** search
- >A wheel that frequently gets reinvented is how to tell the time over networks.
- >Much work has been done on this subject in the ARPA Internet from back when
- >there was only the ARPANET up to a few months ago. This article is a brief
- >summary of the existing methods.
-
- I've gotten more than half a dozen requests to post the time RFCs
- to mod.sources and no requests not to, so I will do so soon.
-
- Volume-Number: Volume 5, Number 20a
-
- >From jsq Wed Jan 22 16:25:52 1986
- From: std-unix%ut-sally.UUCP@SALLY.UTEXAS.EDU (Moderator, John Quarterman)
- Newsgroups: mod.std.unix
- Subject: Re: TZ and TERM per process
- Message-Id: <4029@ut-sally.UUCP>
- Organization: IEEE/P1003 Portable Operating System Environment Committee
- Date: 22 Jan 86 22:25:10 GMT
- Apparently-To: std-unix-archive
-
- [ 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 5, Number 20b
-
-