touch command in perl script

I want to run touch a file command like the following.  The file name is parameter passed into a perl script.  How to write the following?  Thanks.

touch $ARGV[0]  
ewang1205Asked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
gremwellConnect With a Mentor Commented:
The problem is that utime() function does not create a file. The attached code should do the job. To get more details about what particular function of class does try 'perldoc' command (i.e. 'perldoc IO::File' or 'perldoc -f utime').

#!/usr/bin/perl -w

use strict;
use IO::File;

my $fname = shift @ARGV;

unless (-f $fname) {
	my $f = new IO::File($fname, "a") || die "open: $!";
	$f->close();
}

my $now = time();
utime($now, $now, $fname) || die "utime: $!";

Open in new window

0
 
Michael DyerSenior Systems Support AnalystCommented:
Try this
                 #!/usr/bin/perl
                 $now = time;
                 utime $now, $now, @ARGV;
0
 
ewang1205Author Commented:
What does your script do?  Thanks.
0
Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
jeromeeCommented:
From the Perl doc:
 utime LIST
             Changes the access and modification times on each
             file of a list of files.  The first two elements of
             the list must be the NUMERICAL access 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 already exist
             and belong to the user running the program:

                 #!/usr/bin/perl
                 $atime = $mtime = time;
                 utime $atime, $mtime, @ARGV;

             Since perl 5.7.2, if the first two elements of the
             list are "undef", then 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) and will even
             work on other users' files where you have write
             permission:

                 utime undef, undef, @ARGV;

             Under NFS this will use the time of the NFS server,
             not the time of the local machine.  If there is a
             time synchronization problem, the NFS server and
             local machine will have different times.  The Unix
             touch(1) command will in fact normally use this form
             instead of the one shown in the first example.

             Note that only passing one of the first two elements
             as "undef" will be equivalent of passing it as 0 and
             will not have the same effect as described when they
             are both "undef".  This case will also trigger an
             uninitialized warning.
0
 
ewang1205Author Commented:
I don't see it can solve my original issue though.  Thanks.
0
 
jeromeeConnect With a Mentor Commented:
Sorry, ewang1205.
I didn't realize that you wanted to use touch to create an empty file... which's not touch's primary function.

User Commands                                            touch(1)

NAME
     touch, settime - change file access and modification times

SYNOPSIS
     touch [-acm] [-r ref_file | -t time]  file...

     touch [-acm] [date_time] file...

     settime [-f ref_file] [date_time] file...

0
 
ewang1205Author Commented:
Thanks.  Yes, I want to use touch to create a file.  I am testing gremwell's solution.  
0
 
FishMongerConnect With a Mentor Commented:
A simpler version of gremwell's solution is:


die "no filename specified" unless @ARGV;
open my $file, '>', $ARGV[0] or die "can't create '$ARGV[0]' $!";

Open in new window

0
 
vikaskhoriaCommented:
If you just want to use the touch command as a unix command then you can use system as well.

Try this:

system("touch ".$ARGV[0]);

Read more on this at:
http://www.perlhowto.com/executing_external_commands
0
 
ozoConnect With a Mentor Commented:
Unlike touch,
open my $file, '>', $ARGV[0]
will truncate a file if it exists.

If portability and efficiency is not an issue, you could do
system "touch $ARGV[0]";
0
 
gremwellCommented:
> system("touch ".$ARGV[0]);
> system "touch $ARGV[0]";

Just for the sake of correctness -- the code above may have difficulties handling some special cases, such as file names containing white spaces and file names starting with dash character. To cover for it, system() should be invoked as following: system("touch", "--", $ARGV[0]);
0
 
ozoCommented:
If the touch command is considered the standard of correctness, the code above handles those cases the same way that the touch command does.
It might be argued that
system "touch",@ARGV;
would be more correct, but the original specification did not state anything beyond $ARGV[0] should be interpreted
0
 
Frederick McIntyreConnect With a Mentor ProgrammerCommented:
Anything wrong with just back ticks?
`touch -- "$ARGV[0]"`

using -- and quotes to deal with files starting with a dash, and with white space.



0
 
gremwellCommented:
@ozo: You are right, ewang1205 has asked for equivalent of UNIX touch command, perhaps he wanted to simulate all its quirks as well.

@fredmc: As a matter of fact, the back ticks example will have problems with file names containing double quotes ;).
0
 
access_choudharyCommented:
Suggest you add utime in addition to open/close, since if the file already exists you don't need to open and close it, you can simply call the utime built-in function to change its access and modification times.

Other way is to use  Shell::Command wrapper around ExtUtils::Command

use Shell::Command;
touch @files;
0
 
ewang1205Author Commented:
Thanks for all the help.  I have not tested each cases yet.  But, I think most of them will work fine.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.