10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I want to run find and wondering if it struggles when there are many files. I have tried
and does not seem to complain.
Is this correct? (8 Replies)
Discussion started by: kristinu
8 Replies
2. UNIX for Beginners Questions & Answers
Hi All,
Whenever i get 10 files(file names like sales*) then another file need to create.
May i know how to implement this in KSH. (4 Replies)
Discussion started by: siddireddy
4 Replies
3. Shell Programming and Scripting
Hi,
I am unable to achieve the file exist conditions if there are multiple files same similar name for e.g. in a $Direct i am having files like
aus.txt
aus.txt_pr
aus.txt_2012
i need to put a file exist condition like which is not working
then
echo "File present"
but the... (9 Replies)
Discussion started by: rohit_shinez
9 Replies
4. Shell Programming and Scripting
Hi all!
I need some help with a script, but I want to make it better, my script prints the last two files on each directory:
echo " "
echo "******************* mediation_sgsn:***********************"
ls -lrt /moneta_collected03/mediation_sgsn | tail -2
echo " "
echo... (6 Replies)
Discussion started by: fretagi
6 Replies
5. UNIX for Dummies Questions & Answers
I have a setup where I have two drives.
TV
TVbackup
For what ever reason, I have a lot of content on my TVbackup drive which isn't on my TV drive.
I want to copy all the files across which are on TVbackup but are not currently on TV.
If there is a file with the same name but a... (2 Replies)
Discussion started by: Spadez
2 Replies
6. Shell Programming and Scripting
Hi,
I am new to shell-scripting, and doing a lot of reading. I am having some trouble getting started with a simple testing of scripting. I have been experimenting with if, loops, for, test, etc., but still unsure. I seem to have the hang of it when it comes to creating a single file or... (6 Replies)
Discussion started by: me2
6 Replies
7. Shell Programming and Scripting
I have the following data stored in a file.
1 /home/file13 /home/file2
2 /home/file41 /home/file654
3 /home/file61 /home/file45
4 /home/file81 /home/file43
...
I want to print the first column provided the files represented by the second and third column exist.
How to do that? (3 Replies)
Discussion started by: kevintse
3 Replies
8. Shell Programming and Scripting
In a directory a number of files named res0.om res1.om ... resN.om
where N can be any unknown number between 1 and 999
Please help me filling out the gaps in the following csh script:
I need to delete all files exept res0.om The easy way is
rm res1*
rm res2*
rm res3*
rm res4*... (5 Replies)
Discussion started by: pederlol
5 Replies
9. Shell Programming and Scripting
I have a process run weekly where I must convert data formats for about thirty files. I read a text file that provides all of the filenames and switch settings.
My perl code is:
for ($j = 1; $j <= $k; $j++)
{
open(FIN2,$fin2) || die "open: $!";
do other stuff
}
Every once in... (2 Replies)
Discussion started by: joeyg
2 Replies
10. Shell Programming and Scripting
Hi,
I would like to perform bash which would check the file A.txt to be size 0 or not. If the size is 0, I would copy file B.txt to replace A.txt.
Please help.
Thanks.
-Jason (6 Replies)
Discussion started by: ahjiefreak
6 Replies
Test::Compile(3pm) User Contributed Perl Documentation Test::Compile(3pm)
NAME
Test::Compile - Check whether Perl module files compile correctly
SYNOPSIS
#!perl -w
use strict;
use warnings;
use Test::Compile;
all_pm_files_ok();
DESCRIPTION
"Test::Compile" lets you check the validity of a Perl module file or Perl script file, and report its results in standard "Test::Simple"
fashion.
BEGIN {
use Test::Compile tests => $num_tests;
pm_file_ok($file, "Valid Perl module file");
}
It's probably a good idea to run this in a BEGIN block. The examples below omit it for clarity.
Module authors can include the following in a t/00_compile.t file and have "Test::Compile" automatically find and check all Perl module
files in a module distribution:
use Test::More;
eval "use Test::Compile 0.09";
Test::More->builder->BAIL_OUT(
"Test::Compile 0.09 required for testing compilation") if $@;
all_pm_files_ok();
You can also specify a list of files to check, using the "all_pm_files()" function supplied:
use strict;
use Test::More;
eval "use Test::Compile 0.09";
Test::More->builder->BAIL_OUT(
"Test::Compile 0.09 required for testing compilation") if $@;
my @pmdirs = qw(blib script);
all_pm_files_ok(all_pm_files(@pmdirs));
Or even (if you're running under Apache::Test):
use strict;
use Test::More;
eval "use Test::Compile 0.09";
Test::More->builder->BAIL_OUT(
"Test::Compile 0.09 required for testing compilation") if $@;
my @pmdirs = qw(blib script);
use File::Spec::Functions qw(catdir updir);
all_pm_files_ok(
all_pm_files(map { catdir updir, $_ } @pmdirs)
);
Why do the examples use "BAIL_OUT()" instead of "skip_all()"? Because testing whether a module compiles is important. "skip_all()" is ok to
use with Test::Pod, because if the pod is malformed the program is still going to run. But checking whether a module even compiles is
something else. Test::Compile should be mandatory, not optional.
FUNCTIONS
"pm_file_ok(FILENAME[, TESTNAME ])"
"pm_file_ok()" will okay the test if the Perl module compiles correctly.
When it fails, "pm_file_ok()" will show any compilation errors as diagnostics.
The optional second argument "TESTNAME" is the name of the test. If it is omitted, "pm_file_ok()" chooses a default test name "Compile
test for FILENAME".
"pl_file_ok(FILENAME[, TESTNAME ])"
"pl_file_ok()" will okay the test if the Perl script compiles correctly. You need to give the path to the script relative to this
distribution's base directory. So if you put your scripts in a 'top-level' directory called script the argument would be
"script/filename".
When it fails, "pl_file_ok()" will show any compilation errors as diagnostics.
The optional second argument "TESTNAME" is the name of the test. If it is omitted, "pl_file_ok()" chooses a default test name "Compile
test for FILENAME".
"all_pm_files_ok([@files/@directories])"
Checks all the files in @files for compilation. It runs all_pm_files() on each file/directory, and calls the "plan()" function for you
(one test for each function), so you can't have already called "plan".
If @files is empty or not passed, the function finds all Perl module files in the blib directory if it exists, or the lib directory if
not. A Perl module file is one that ends with .pm.
If you're testing a module, just make a t/00_compile.t:
use Test::More;
eval "use Test::Compile 0.09";
plan skip_all => "Test::Compile 0.09 required for testing compilation"
if $@;
all_pm_files_ok();
Returns true if all Perl module files are ok, or false if any fail.
Or you could just let Module::Install::StandardTests do all the work for you.
"all_pl_files_ok([@files])"
Checks all the files in @files for compilation. It runs pl_file_ok() on each file, and calls the "plan()" function for you (one test
for each file), so you can't have already called "plan".
If @files is empty or not passed, the function uses all_pl_files() to find scripts to test
If you're testing a module, just make a t/00_compile_scripts.t:
use Test::More;
eval "use Test::Compile 0.09";
plan skip_all => "Test::Compile 0.09 required for testing compilation"
if $@;
all_pl_files_ok();
Returns true if all Perl module files are ok, or false if any fail.
"all_pm_files([@dirs])"
Returns a list of all the perl module files - that is, files ending in .pm - in $dir and in directories below. If no directories are
passed, it defaults to blib if blib exists, or else lib if not. Skips any files in "CVS" or ".svn" directories.
The order of the files returned is machine-dependent. If you want them sorted, you'll have to sort them yourself.
"all_pl_files([@files/@dirs])"
Returns a list of all the perl script files - that is, files ending in .pl or with no extension. Directory arguments are searched
recursively . If arguments are passed, it defaults to script if script exists, or else bin if bin exists. Skips any files in "CVS" or
".svn" directories.
The order of the files returned is machine-dependent. If you want them sorted, you'll have to sort them yourself.
AUTHORS
Sagar R. Shah "<srshah@cpan.org>", Marcel Gruenauer, "<marcel@cpan.org>", Evan Giles, "<egiles@cpan.org>"
COPYRIGHT AND LICENSE
Copyright 2007-2012 by the authors.
This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
SEE ALSO
Test::LoadAllModules just handles modules, not script files, but has more fine-grained control.
perl v5.14.2 2012-02-27 Test::Compile(3pm)