Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!ames!sdcsvax!ucbvax!CS.ROCHESTER.EDU!becker
From: becker@CS.ROCHESTER.EDU
Newsgroups: comp.windows.x
Subject: Re: xmh and utime()
Message-ID: <8709222129.AA00357@wasat.cs.rochester.edu>
Date: Tue, 22-Sep-87 19:07:35 EDT
Article-I.D.: wasat.8709222129.AA00357
Posted: Tue Sep 22 19:07:35 1987
Date-Received: Thu, 24-Sep-87 07:29:15 EDT
References: <8709222111.AA16569@gilroy.dec.com>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 20


   According to man utime (on an Ultrix 2.0 system), if the second
   argument to utime is a NULL, then the access and modification times of
   the file are set to the current time.  Sounds like a bug in Sun's utime...

Terry,

We run 4.2bsd, 4.3bsd, and SunOS Unix machines here.  None of the man pages for
utime() list the NULL argument feature.  Looks like it's only in Ultrix (possibly
others?).  I'm glad you replied (as the author of xmh, right?) -- with this info
in mind (not in Sun or 4.3bsd), perhaps you could consider changing the code
in view of better portability.

Thanks for your consideration!

Tim Becker.
becker@cs.rochester.edu

PS.  I love the *speed* of xmh.  I do have some problems with it still, but it
looks wonderful.  Thanks!