Hi,
I am trying to execute the below shell script: script name(ss1).
ss1 was given permission - 744 before executing.
name: ss1
#ss1
#usage:ss1
ls
who
pwd
:wq
I tried to execute $ss1 (Enter)
Its not executing.... It says that ss1 is not found:
echo $SHELL. The o/put i got is... (5 Replies)
I am trying to run a shell script using the ./<ScriptName> command, but the server returns an error bash: ./Script1.sh: Permission denied
What variable do I need to set to avoid this? (4 Replies)
Hi,
I need to write a shell script that executes the command
uname -a
the output i get is of the format :
FreeBSD test.trial.machine.com 4.5-RELEASE FreeBSD 4.5-RELEASE #0: Mon Jan 28 14:31:56 GMT 2000 tester@builder.freebsdmall.com:/usr/src/sys/compile/GENERIC i386
(this is all in a... (3 Replies)
Hi,
Could anyone please tell me what are basic diffrence between a shell and a perl scipt i.e where to use shell scripting and where perl scripting? I want to know advantages of shell script over perl script and advantage of perl script over shell script.
Thanks,
Yogi (3 Replies)
I need to execute a shell script kept in unix machine from windows. User id, password area available.
For eg.
There's a shell script wich moves all the logs kept in my home directory to a directory named LOGS.
Now i need to get this done through windows; either using a batch file, or java... (4 Replies)
Hi All,
I have a requirement to mv a file in unix from plsql procedure.
for that i have created a java host procedure, a host_command, given all grants as per ORACLE-BASE - Oracle8i Shell Commands From PL/SQL
but i am getting an error ""Process err :/bin/sh: mv Not Found""
kindly let me... (1 Reply)
I have written this script. This is used for creating a backup folder.
#!/bin/sh
#set -x
. /home/.profile
usage="Usage is $0"
usage="$usage "
# Use the getopt utility to set up the command line flags.
set -- `/usr/bin/getopt b: $*`
# Process individual command line arguments
while ;... (1 Reply)
Platform : Solaris 10, RHEL 5.4, OEL 6
I've noticed that some of my colleagues execute scripts by typing sh before the script name
sh myscript.shI always execute a script by typing the script name and typing enter provided PATH variable has . (current directory) in it
myscript.sh (and... (1 Reply)
Hi All,
I wanted to know why we use the '-f' option while executing script.
in my case...
abcd.sh -f any_evts 02 2014
abcd = Scriptname
-f = dont know
any_evts = Some file or string
02= month
2014 = year
So in above pleas ehelp to understand here -f and other arguement like... (1 Reply)
Discussion started by: ajju
1 Replies
LEARN ABOUT DEBIAN
test::assertions::testscript
Test::Assertions::TestScript(3pm) User Contributed Perl Documentation Test::Assertions::TestScript(3pm)NAME
Test::Assertions::TestScript - Base for test scripts
SYNOPSIS
use Test::Assertions::TestScript;
use Module::To::Test qw( frobnicate );
ASSERT(frobnicate(),"Frobnicate returns true");
DESCRIPTION
Test::Assertions::TestScript provides a base for writing test scripts. It performs some common actions such as setting up the @INC path and
parsing command-line options, specifically:
o The lib and t/lib directories are added to @INC.
o The current directory is changed to the directory the script is in.
o Test script command-line options are parsed. (See "COMMAND-LINE OPTIONS")
o The test set of functions from Test::Assertions are imported into your test script.
Test::Assertions::TestScript makes certain assumptions about the filesystem layout of your project:
o Modules that you are testing are in the lib directory of your project.
o Test scripts are in the t directory.
o There may also be a t/lib directory for any modules written for the test process.
Test::Assertions::TestScript should be "use"d before any modules that you intend to test.
OPTIONS
Options can be supplied to the import function. These should be placed after the "use" or "import". For example
use Test::Assertions::TestScript( tests => 10, options => { 'b', $opt_b })
The following options are defined:
tests
The number of tests to pass to "plan tests" from Test::Assertions. For example to tell Test::Assertions::TestScript that the script
contains 42 tests:
use Test::Assertions::TestScript tests => 42;
options
A hashref of additional options to capture via Getopt::Long. The "options" import parameter is passed verbatim to GetOptions, so
something along the following lines is required in order to capture the "-b" command line option:
use Test::Assertions::TestScript( options => { 'b' => $opt_b } );
COMMAND-LINE OPTIONS
A script based on Test::Assertions::TestScript will detect the following command line options.
-t Shallow tracing. Traces are "print"ed and AutoImport is turned on.
-T Deep tracing. Traces are "print"ed and AutoImport is turned on.
--trace-module=MODULE
Imports tracing into MODULE specifically. Can be specified multiple times.
-s Save generated output. You will need to write the actual code to do this in your testscript, but you can inspect
$Test::Assertions::TestScript::SAVE_OUTPUT to see whether this argument was given.
Be aware that all other command line options will be disregarded unless the "options" import parameter is used to capture them.
VERSION
$Revision: 1.18 $
AUTHOR
Colin Robertson <cpan _at_ bbc _dot_ co _dot_ uk>
COPYRIGHT
(c) BBC 2005-6. This program is free software; you can redistribute it and/or modify it under the GNU GPL.
See the file COPYING in this distribution, or http://www.gnu.org/licenses/gpl.txt
perl v5.10.0 2006-08-10 Test::Assertions::TestScript(3pm)