d/freebsd-skq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
c55d515408
freebsd-skq/share/man/man9/time.9

141 lines
4.1 KiB
Groff
Raw Normal View History

Add time(9) to document the kernel time variables. Obtained from NetBSD and then modified by me to reflect some FreeBSD specific things and to clarify some other pointed based on some old mail from Bruce Evans about this man page.
1997-03-22 19:09:31 +00:00
.\" $NetBSD: time.9,v 1.1 1995/11/25 21:24:53 perry Exp $
.\"
.\" Copyright (c) 1994 Christopher G. Demetriou
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\" notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\" notice, this list of conditions and the following disclaimer in the
.\" documentation and/or other materials provided with the distribution.
.\" 3. All advertising materials mentioning features or use of this software
.\" must display the following acknowledgement:
.\" This product includes software developed by Christopher G. Demetriou
.\" for the NetBSD Project.
.\" 3. The name of the author may not be used to endorse or promote products
.\" derived from this software without specific prior written permission
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.\"
$Id$ -> $FreeBSD$
1999-08-28 00:22:10 +00:00
.\" $FreeBSD$
Add $Id$, to make it simpler for members of the translation teams to track. The $Id$ line is normally at the bottom of the main comment block in the man page, separated from the rest of the manpage by an empty comment, like so; .\" $Id$ .\" If the immediately preceding comment is a @(#) format ID marker than the the $Id$ will line up underneath it with no intervening blank lines. Otherwise, an additional blank line is inserted. Approved by: bde
1999-07-12 21:02:10 +00:00
.\"
Add time(9) to document the kernel time variables. Obtained from NetBSD and then modified by me to reflect some FreeBSD specific things and to clarify some other pointed based on some old mail from Bruce Evans about this man page.
1997-03-22 19:09:31 +00:00
.Dd March 22, 1997
.Dt TIME 9
mdoc(7) police: removed HISTORY info from the .Os call.
2001-07-10 15:31:11 +00:00
.Os
Add time(9) to document the kernel time variables. Obtained from NetBSD and then modified by me to reflect some FreeBSD specific things and to clarify some other pointed based on some old mail from Bruce Evans about this man page.
1997-03-22 19:09:31 +00:00
.Sh NAME
.Nm boottime ,
.Nm mono_time ,
.Nm runtime ,
.Nm time
.Nd system time variables
.Sh SYNOPSIS
Avoid use of direct troff requests in mdoc(7) manual pages.
2000-11-10 17:46:15 +00:00
.Bl -item -compact
.It
.Va extern struct timeval boottime ;
.It
.Va extern volatile struct timeval mono_time ;
.It
.Va extern struct timeval runtime ;
.It
.Va extern struct timeval time ;
.El
Add time(9) to document the kernel time variables. Obtained from NetBSD and then modified by me to reflect some FreeBSD specific things and to clarify some other pointed based on some old mail from Bruce Evans about this man page.
1997-03-22 19:09:31 +00:00
.Sh DESCRIPTION
The
.Va time
variable is the system's
.Dq wall time
clock.
It is set at boot by
.Xr inittodr 9 ,
and is updated by the
.Xr settimeofday 2
system call and by periodic clock interrupts.
.Pp
The
.Va boottime
variable holds the system boot time. It is set from
.Va time
at system boot, and is updated when the system time is adjusted
with
.Xr settimeofday 2 .
.Pp
The
.Va runtime
variable holds the time that the system switched to the
current process.
Removed whitespace at end-of-line; no content changes. I simply did cd src/share; find man[1-9] -type f|xargs perl -pi -e 's/[ \t]+$//' BTW, what editors are the culprits? I'm using vim and it shows me whitespace at EOL in troff files with a thick blue block... Reviewed by: Silence from cvs diff -b MFC after: 7 days
2001-07-14 19:41:16 +00:00
It is set after each context switch,
Add time(9) to document the kernel time variables. Obtained from NetBSD and then modified by me to reflect some FreeBSD specific things and to clarify some other pointed based on some old mail from Bruce Evans about this man page.
1997-03-22 19:09:31 +00:00
and is updated when the system time is adjusted with
.Xr settimeofday 2 .
Because
.Va runtime
is used for system accounting, it is set with the high-resolution
.Xr microtime 9
function, rather than being copied from
.Va time .
.Pp
The
.Va mono_time
variable is a monotonically increasing system clock. It is set
from
.Va time
at boot, and is updated by the periodic timer interrupt. (It is
not updated by
Prepare for mdoc(7)NG.
2001-01-16 09:32:40 +00:00
.Xr settimeofday 2 . )
Add time(9) to document the kernel time variables. Obtained from NetBSD and then modified by me to reflect some FreeBSD specific things and to clarify some other pointed based on some old mail from Bruce Evans about this man page.
1997-03-22 19:09:31 +00:00
.Pp
All of these variables contain times
expressed in seconds and microseconds since midnight (0 hour),
January 1, 1970.
.Pp
Clock interrupts should be blocked
when reading or writing
.Va time
or
.Va mono_time ,
because those variables are updated by
.Fn hardclock .
The
.Xr gettime 9
function can be used to read the
.Va time
variable in an atomic manner. There is no equivalent
function for accessing
mdoc(7) police: split punctuation characters + misc fixes.
2001-02-01 16:38:02 +00:00
.Va mono_time .
Add time(9) to document the kernel time variables. Obtained from NetBSD and then modified by me to reflect some FreeBSD specific things and to clarify some other pointed based on some old mail from Bruce Evans about this man page.
1997-03-22 19:09:31 +00:00
The
.Va boottime
and
.Va runtime
variables may be read and written without special precautions.
.Pp
It should be noted that due to the differences in how the time values
returned by
.Xr gettime 9
and
.Xr microtime 9
Removed whitespace at end-of-line; no content changes. I simply did cd src/share; find man[1-9] -type f|xargs perl -pi -e 's/[ \t]+$//' BTW, what editors are the culprits? I'm using vim and it shows me whitespace at EOL in troff files with a thick blue block... Reviewed by: Silence from cvs diff -b MFC after: 7 days
2001-07-14 19:41:16 +00:00
are updated, comparing the results of the two routines
Add time(9) to document the kernel time variables. Obtained from NetBSD and then modified by me to reflect some FreeBSD specific things and to clarify some other pointed based on some old mail from Bruce Evans about this man page.
1997-03-22 19:09:31 +00:00
may result in a time value that appears to go backwards.
This can be avoided by consistently using one function or the other
for use in any given context.
.Sh SEE ALSO
.Xr settimeofday 2 ,
.Xr gettime 9 ,
.\" .Xr hardclock 9 ,
mdoc(7) police: sort SEE ALSO xrefs (sort -b -f +2 -3 +1 -2).
2001-07-06 16:46:48 +00:00
.\" .Xr hz 9 ,
Add time(9) to document the kernel time variables. Obtained from NetBSD and then modified by me to reflect some FreeBSD specific things and to clarify some other pointed based on some old mail from Bruce Evans about this man page.
1997-03-22 19:09:31 +00:00
.Xr inittodr 9 ,
.Xr microtime 9
.Sh BUGS
The notion of having a single
.Va runtime
variable obviously would not be appropriate in multiprocessor systems.
Reference in New Issue Copy Permalink