Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site trwrba.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!decvax!ittatc!dcdwest!sdcsvax!sdcrdcf!trwrb!trwrba!jsisi
From: jsisi@trwrba.UUCP (Gerald W. Irmler)
Newsgroups: net.sources.bugs
Subject: Re:Re: How do I compile ttype? (times(2))
Message-ID: <1722@trwrba.UUCP>
Date: Tue, 10-Dec-85 01:43:37 EST
Article-I.D.: trwrba.1722
Posted: Tue Dec 10 01:43:37 1985
Date-Received: Thu, 12-Dec-85 05:19:07 EST
References: <965@turtlevax.UUCP> <13500001@hpspkla.UUCP> <1752@teddy.UUCP> <1929@elecvax.eecs.unsw.oz> <1641@utah-gr.UUCP>
Reply-To: jsisi@trwrba.UUCP (Dan Jones)
Organization: TRW EDS, Redondo Beach, CA
Lines: 16
Keywords: times
Summary: wrong info was given


The referenced article stated the System V times call returned the CPU time.

I haven't looked at the code, but I quote from the times(2) manual page:

"Upon successful completion, *times* returns the elaspsed real time, in HZ,
since an arbitrary time in the past (e.g. system start-up time).
This point does not change from one invocation of *times* to another."

Thus I think one can use times(2) to fake a suitable ftime unless the manual
page is in error.

	Dan Jones
	ihnp4!trwrb!jcc-one!djones
	NOT the path in the header.