Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!nbires!hao!noao!mcdsun!comvme!jlm
From: jlm@comvme.UUCP (Jeff Morris)
Newsgroups: comp.windows.x
Subject: Re: xmh and utime()
Message-ID: <527@comvme.UUCP>
Date: Wed, 23-Sep-87 14:21:32 EDT
Article-I.D.: comvme.527
Posted: Wed Sep 23 14:21:32 1987
Date-Received: Sat, 26-Sep-87 06:17:39 EDT
References: <8709222111.AA16569@gilroy.dec.com> <8709222129.AA00357@wasat.cs.rochester.edu>
Reply-To: jlm@comvme.UUCP (Jeff Morris)
Organization: Motorola Microcomputer Division, Tempe, Az.
Lines: 54

In article <8709222129.AA00357@wasat.cs.rochester.edu> becker@CS.ROCHESTER.EDU writes:
>
>   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!

Newsgroups: comp.windows.x
Subject: Re: xmh and utime()
Summary: System V
Expires: 
References: <8709222111.AA16569@gilroy.dec.com> <8709222129.AA00357@wasat.cs.rochester.edu>
Sender: 
Reply-To: jlm@comvme.UUCP (Jeff Morris)
Followup-To: 
Distribution: world
Organization: Motorola Microcomputer Division, Tempe, Az.
Keywords: 

.In article <8709222129.AA00357@wasat.cs.rochester.edu> becker@CS.ROCHESTER.EDU writes:
.>
.>   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
...
.>
.>Tim Becker.
.>becker@cs.rochester.edu

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.