Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!husc6!necntc!ames!sdcsvax!ucbvax!CS.UCLA.EDU!bilbo.geoff
From: bilbo.geoff@CS.UCLA.EDU.UUCP
Newsgroups: comp.windows.x
Subject: Re: xmh and utime()
Message-ID: <8709250751.AA03504@ATHENA.MIT.EDU>
Date: Thu, 24-Sep-87 21:28:41 EDT
Article-I.D.: ATHENA.8709250751.AA03504
Posted: Thu Sep 24 21:28:41 1987
Date-Received: Sat, 26-Sep-87 15:27:55 EDT
References: <527@comvme.UUCP>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 14

> According to the man page for utime(2), System V, a NULL parm for times 
> means use the current time, just as with Ultrix, above.  

> My manual for SYSTEM V/68 (R3V3) mentions the same thing.  

The proper manual for looking up this sort of thing is neither SV, Ultrix,
nor BSD, but rather V7.  If you don't write for the lowest common denominator,
you can expect troubles.  (And yes, I'm aware that V7 isn't really a perfectly
common denominator either, but at least it's close.)

A perfect example of this is the common penchant for using setitimer, even
when alarms would do just as well.

	Geoff Kuenning	geoff@lcc.ucla.edu	geoff@ITcorp.com