Before I answer your question I shall point you towards unlink which is a perl function for removing files. As for using variables in system the issue is that the variable in question is being interpolated as $date_more_filename (so nothing to do with the function). So what you need to do is delimit the variable name which you can do by surrounding it in curly braces e.g
my $date = "Tuesday the 8th of 2003";
## note the {} around the variable name
print "Today is ${date}\n";
__output__
Today is Tuesday the 8th of 2003
See. perlop for more info on quoting in perl.
HTH
_________
broquaint | [reply]
[d/l] |
The problem is that Perl is trying to substitute $date_more_filename, not $date.
you want ${date}_more_filename.
use strict would have caught this.
-pete
"Worry is like a rocking chair. It gives you something to do, but it doesn't get you anywhere." | [reply] |
system "rm /storage/filename${date}_more_filename.csv";
hope this helps
thinker | [reply]
[d/l] |
You could try building up the command string as follows
my $cmd = join('', 'rm /storage/filename', $date, '_more_filename.csv'
+);
system ($cmd);
HTH | [reply]
[d/l] |
Environmental Variables from Perl
Maybe I'm missing something here, but look at the following
code sniglet:
--$ cat bite.pl
$ENV{verb}="bite";
system 'echo ${verb}_me';
When I run this I get:
--$ perl bite.pl
bite_me
Maybe this will solve the problem?
HTH
| Peter L. Berghold | Brewer of Belgian Ales |
| Peter@Berghold.Net | www.berghold.net |
| Unix Professional |
| [reply] |
system LIST
system PROGRAM LIST
Does exactly the same thing as exec LIST, except that a fork is done first, and the parent process waits for the child process to complete. Note that argument processing varies depending on the number of arguments. If there is more than one argument in LIST, or if LIST is an array with more than one value, starts the program given by the first element of the list with arguments given by the rest of the list. If there is only one scalar argument, the argument is checked for shell metacharacters, and if there are any, the entire argument is passed to the system's command shell for parsing (this is /bin/sh -c on Unix platforms, but varies on other platforms). If there are no shell metacharacters in the argument, it is split into words and passed directly to execvp, which is more efficient.
Beginning with v5.6.0, Perl will attempt to flush all files opened for output before any operation that may do a fork, but this may not be supported on some platforms. To be safe, you may need to set $| ($AUTOFLUSH in English) or call the autoflush() method of IO::Handle on any open handles.
The return value is the exit status of the program as returned by the wait call. To get the actual exit value shift right by eight (see below). See also /exec. This is not what you want to use to capture the output from a command, for that you should use merely backticks or qx//, as described in perlop/"`STRING`". Return value of -1 indicates a failure to start the program (inspect $! for the reason).
Like exec, system allows you to lie to a program about its name if you use the system PROGRAM LIST syntax.
Because system and backticks block SIGINT and SIGQUIT, killing the program they're running doesn't actually interrupt your program.
@args = ("command", "arg1", "arg2");
system(@args) == 0
or die "system @args failed: $?"
You can check all the failure possibilities by inspecting $? like this:
$exit_value = $? >> 8;<br>
$signal_num = $? & 127;<br>
$dumped_core = $? & 128; <br>
or more portably by using the W*() calls of the POSIX extension.
When the arguments get executed via the system shell, results and return codes will be subject to its quirks and capabilities.
| [reply]
[d/l]
[select] |