10-18-2006
Hi shereenmotor
thank you
without redirect to txt file i get the dir listing echoed back to me.
when I keep the redirect I get no error message at all and nothing is written to my dirList.txt file.
when I put
find `pwd` -type d | grep TESTINGDIR 2> dirList.txt
I get the dir listing redirected to stdout i.e. echoed back to me
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hey there, I'm a total newbie unix guy here and just picking this stuff up. Have a very small script I put together that works fine from the command line but not once I put it in a cron job. Searched and found this thread and am wondering it it has something to do with setting variables, though the... (7 Replies)
Discussion started by: JackTheTripper
7 Replies
2. Shell Programming and Scripting
i would like to make a shell script (red hat 9 cmd line only)
to telnet to my local isp's webmail server on port 25 and send it commands
such as helo :) help would be much appreciated, and i found no posts similar that answered my question... the closest i've gotten to an answer from about 8... (3 Replies)
Discussion started by: kypeswith
3 Replies
3. Shell Programming and Scripting
Hi all-
I'm trying to search through some .gz log files to verify certain feeds have passed through our app.
I have a small script that I wrote in hopes that I could automate the checking but haven't been able to get the zgrep to work. When I copy it to the command line directly it works... (2 Replies)
Discussion started by: Cailet
2 Replies
4. Shell Programming and Scripting
When I run this code from the command line works
spinel.middlebury.edu:/u02/sct/banner/bandev2/middlebury/shl:DEV2$ ls ef*
eftseq.dat
spinel.middlebury.edu:/u02/sct/banner/bandev2/middlebury/shl:DEV2$ file_seq=$( < eftseq.dat) ... (1 Reply)
Discussion started by: rechever
1 Replies
5. Shell Programming and Scripting
/usr/bin/find $SEARCH_DIR -daystart \( \( -name 'KI*' -a -name '*.csv' \) -o -name '*_xyz_*' \) -mtime $DAYS_AGO -printf %f -printf "\n" | sort -r > $FILES
The above command gives different results when run on a cron job. When run manually the result is accurate. (2 Replies)
Discussion started by: nuthalapati
2 Replies
6. Shell Programming and Scripting
Hi all .... vexing problem here ...
I am using sed to replace some special characters in a .txt file:
sed -e 's/_<ED>_/_355_/g;s/_<F3>_/_363_/g;s/_<E1>_/_341_/g' filename.txt
This command replaces <ED> with í , <F3> with ó and <E1> with á.
When I run the command to standard output, it works... (1 Reply)
Discussion started by: crumplecrap
1 Replies
7. UNIX for Dummies Questions & Answers
Hey guys. Hopefully this is an easy one but having reference similar problems on the web I still can't fix it.
I am doing a recursive find and replace from a script. Of course I could just run the damn thing from the command line but it's bugging me now and want to get it working.
grep -rl... (4 Replies)
Discussion started by: anthonyjstewart
4 Replies
8. UNIX for Advanced & Expert Users
OK , ..
This is an odd one. I have a new server and I need to have a tunnel open to it.
I have this exact process running on a few others but this new one I just got is not allowing the script to connect.
I set up my users account and ssh keys
from the server that will host the tunneling i... (6 Replies)
Discussion started by: jeffsandman0035
6 Replies
9. Windows & DOS: Issues & Discussions
Hi All,
This command works when I type it on but when I run the batch file it doesn't..any ideas why?
attrib.exe * | find /c /v "" >filecount.txt (1 Reply)
Discussion started by: Grueben
1 Replies
10. Shell Programming and Scripting
OSX 10.9
I am building a script that evaluates the difference between 2 files. Here is a command that does not work transparently.
Running this command in Terminal yields great results; however when I put that line in a .sh script, I get the errors shown below. Am I doing something silly?
... (1 Reply)
Discussion started by: sudo
1 Replies
LEARN ABOUT DEBIAN
test::lectrotest::regressiontesting
Test::LectroTest::RegressionTesting(3pm) User Contributed Perl Documentation Test::LectroTest::RegressionTesting(3pm)
NAME
Test::LectroTest::RegressionTesting - How to do regression testing (for free!)
SYNOPSIS
use Test::LectroTest
regressions => "regressions.txt";
# -- OR --
use Test::LectroTest
playback_failures => "regression_suite_for_my_module.txt",
record_failures => "failures_in_the_field.txt";
# -- OR --
use Test::LectroTest::Compat
regressions => "regressions.txt";
# -- OR --
use Test::LectroTest::Compat
playback_failures => "regression_suite_for_my_module.txt",
record_failures => "failures_in_the_field.txt";
DESCRIPTION
Say that LectroTest uncovers a bug in your software by finding a random test case that proves one of your properties to be false. If you
apply a fix for the bug, how can you be sure that LectroTest will re-test the property using the exact same test case that "broke" it
before, just to be certain the bug really is fixed? And how can you be sure that future changes to your code will not reintroduce the same
bug without your knowing it?
For situations like these, LectroTest can record failure-causing test cases to a file, and it can play those test cases back as part of its
normal testing strategy.
The easiest way to take advantage of this feature is to set the regressions parameter when you "use" Test::LectroTest or
Test::LectroTest::Compat:
use Test::LectroTest
regressions => "regressions.txt";
This tells LectroTest to use the file "regressions.txt" for both recording and playing back failures. If you want to record and play back
from separate files, use the record_failures and playback_failures options:
use Test::LectroTest::Compat
playback_failures => "regression_suite_for_my_module.txt",
record_failures => "failures_in_the_field.txt";
Here is how it works:
1. When testing a property named N, LectroTest will check for a play-back file. If the file exists, LectroTest will search it for test
cases associated with N. If any such test cases exist, LectroTest will play them back before and in addition to performing the usual,
random testing of the property.
2. When performing the usual, random testing of a property named N, if a failure occurs (i.e., LectroTest finds a counterexample),
LectroTest will record the test case that caused the failure to the recording file, associating the test case with the name N.
NOTE: If you pass any of the recording or playback parameters to Test::LectroTest::Compat, you must have version 0.3500 or greater of
Test::LectroTest installed. (Module authors, update your modules' build dependencies accordingly.) The Test::LectroTest module itself,
however, has always ignored unfamiliar parameters, and thus these options are backward compatible with older versions.
SEE ALSO
Test::LectroTest gives a quick overview of automatic, specification-based testing with LectroTest. This module accepts failure recording
and play-back options.
Test::LectroTest::Compat lets you mix LectroTest with the popular family of Test::Builder-based modules such as Test::Simple and
Test::More. This module accepts failure recording and play-back options.
LECTROTEST HOME
The LectroTest home is http://community.moertel.com/LectroTest. There you will find more documentation, presentations, mailing-list
archives, a wiki, and other helpful LectroTest-related resources. It's also the best place to ask questions.
AUTHOR
Tom Moertel (tom@moertel.com)
COPYRIGHT and LICENSE
Copyright (c) 2004-06 by Thomas G Moertel. All rights reserved.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
perl v5.12.3 2007-08-30 Test::LectroTest::RegressionTesting(3pm)