PERL PERL5 CHANGES 40 CHANGE 23331 RE PERL 31586 UTIME DOES NOT REACH EXPECTATIONS PATCH
Date: Mon, 20 Sep 2004 15:45:00 -0700

Subject: Change 23331: Re: [perl #31586] utime does not reach expectations [PATCH]
From: davem@no-spam (Dave Mitchell)

Change 23331 by davem@no-spam on 2004/09/20 22:11:29

Subject: Re: [perl #31586] utime does not reach expectations [PATCH]
From: LAUN Wolfgang <wolfgang.laun@no-spam>
Date: Fri, 17 Sep 2004 14:01:11 +0200
Message-Id: <DF27CDCBD2581D4B88431901094E4B4D02B0C88B@no-spam>

Clarify the effect of utime when the file isn't owned by the user
Affected files ...

... //depot/perl/pod/perlfunc.pod#446 edit
Differences ...

==== //depot/perl/pod/perlfunc.pod#446 (text) ====
Index: perl/pod/perlfunc.pod --- perl/pod/perlfunc.pod#445~23184~ Mon Aug 2 09:40:36 2004
+++ perl/pod/perlfunc.pod Mon Sep 20 15:11:29 2004
@@no-spam -6400,7 +6400,8 @@no-spam and modification times, in that order. Returns the number of files successfully changed. The inode change time of each file is set to the current time. For example, this code has the same effect as the -Unix touch(1) command when the files I<already exist>.
+Unix touch(1) command when the files I<already exist> and belong to +the user running the program:
#!/usr/bin/perl $atime = $mtime = time;
@@no-spam -6410,7 +6411,8 @@no-spam the utime(2) function in the C library will be called with a null second argument. On most systems, this will set the file's access and modification times to the current time (i.e. equivalent to the example -above.)
+above) and will even work on other users' files where you have write +permission:
utime undef, undef, @no-spam End of Patch.