hi all
i wrote a shell script which uses perl script my code is :
>cat filename | while read i
>do
>perl -e 'require "/home/scripts/abc.pl" ; abc("$i")'
>done
perl script used will simply check syntax of Cobol programs but it didn't work for me so i asked my colleague he suggested... (1 Reply)
can u explain this step by step........plz...will it do the same
for I in *.tar.gz; do
A=`basename $I .tar.gz`
mkdir $A
cp marking-guide ${A}/$A
cd $A
gunzip -c ../$I | tar xf -
cd..
done
thnx
__________________ (2 Replies)
Hi ,
Can anyone explains what does the below highlighted statements means:
# Set environment variables
. ${0%/*}/wrkenv.sh
jobName_sh=${0##*/}
jobName=${jobName_sh%.*}
Thanks,
Sri (1 Reply)
Hi frnds,
one my frnds has given resolution for my problem as below. it working great , but i couldnt understand somethings in the script.
Why ++ operator after the function calling. how these each block working. will each run for each input line sequencially or one block for all the lines... (9 Replies)
Hi,
Pls explain me what the below code is doing. specially meaning if -a while calling test function-
case $1 in
1) beg_dt=01; end_dt=07 ;;
2) beg_dt=08; end_dt=14 ;;
3) beg_dt=15; end_dt=21 ;;
4) beg_dt=22; end_dt=28 ;;
5) beg_dt=29; end_dt=31 ;;
esac test \( `date +%w` -eq $2 -a... (3 Replies)
Discussion started by: sendtoshailesh
3 Replies
LEARN ABOUT CENTOS
rake
RAKE(1) Ruby Programmers Reference Guide RAKE(1)NAME
rake -- Ruby Make
SYNOPSIS
rake [--f Rakefile] [--version] [-CGNPgnqstv] [-D [PATTERN]] [-E CODE] [-I LIBDIR] [-R RAKELIBDIR] [-T [PATTERN]] [-e CODE] [-p CODE]
[-r MODULE] [--rules] [variable=value] target ...
DESCRIPTION
Rake is a simple ruby(1) build program with capabilities similar to the regular make(1) command.
Rake has the following features:
o Rakefiles (Rake's version of Makefiles) are completely defined in standard Ruby syntax. No XML files to edit. No quirky Makefile syntax
to worry about (is that a tab or a space?).
o Users can specify tasks with prerequisites.
o Rake supports rule patterns to synthesize implicit tasks.
o Flexible FileLists that act like arrays but know about manipulating file names and paths.
o A library of prepackaged tasks to make building rakefiles easier.
OPTIONS --version Display the program version.
-C
--classic-namespace
Put Task and FileTask in the top level namespace
-D [PATTERN]
--describe [PATTERN]
Describe the tasks (matching optional PATTERN), then exit.
-E CODE
--execute-continue CODE
Execute some Ruby code, then continue with normal task processing.
-G
--no-system
--nosystem Use standard project Rakefile search paths, ignore system wide rakefiles.
-I LIBDIR
--libdir LIBDIR Include LIBDIR in the search path for required modules.
-N
--no-search
--nosearch Do not search parent directories for the Rakefile.
-P
--prereqs Display the tasks and dependencies, then exit.
-R RAKELIBDIR
--rakelib RAKELIBDIR
--rakelibdir RAKELIBDIR
Auto-import any .rake files in RAKELIBDIR. (default is rakelib )
-T [PATTERN]
--tasks [PATTERN] Display the tasks (matching optional PATTERN) with descriptions, then exit.
-e CODE
--execute CODE Execute some Ruby code and exit.
-f FILE
--rakefile FILE Use FILE as the rakefile.
-h
--help Prints a summary of options.
-g
--system Using system wide (global) rakefiles (usually ~/.rake/*.rake ).
-n
--dry-run Do a dry run without executing actions.
-p CODE
--execute-print CODE
Execute some Ruby code, print the result, then exit.
-q
--quiet Do not log messages to standard output.
-r MODULE
--require MODULE Require MODULE before executing rakefile.
-s
--silent Like --quiet, but also suppresses the 'in directory' announcement.
-t
--trace Turn on invoke/execute tracing, enable full backtrace.
-v
--verbose Log message to standard output (default).
--rules Trace the rules resolution.
SEE ALSO ruby(1)make(1)
http://rake.rubyforge.org/
REPORTING BUGS
Bugs, features requests and other issues can be logged at <http://onestepback.org/redmine/projects/show/rake>.
You will need an account to before you can post issues. Register at <http://onestepback.org/redmine/account/register>. Or you can send an
email to the author.
AUTHOR
Rake is written by Jim Weirich <jim@weirichhouse.org>
UNIX November 7, 2012 UNIX