10 More Discussions You Might Find Interesting
1. UNIX for Beginners Questions & Answers
Helo
Is there a better way to search within a list of subfolders :
A_START_PATH="/data_1/data_2"
#
# dir2, dir3, dir6, ..... dir59 exists
#
A_LIST="$A_START_PATH/dir1 $A_START_PATH/dir4 $A_START_PATH/dir5"
find "$A_LIST" -type f -name"*.txt"
Now searching for all files in any subdirs... (2 Replies)
Discussion started by: jcdole
2 Replies
2. Shell Programming and Scripting
I have a folder with 4000 (*3) files like
gr_q4_gb-1.anc
gr_q4_gb-1.anc_cdr_st.txt
gr_q4_gb-1.anc_cdr_tr.txt
gr_q4_gb-2.anc
gr_q4_gb-2.anc_cdr_st.txt
gr_q4_gb-2.anc_cdr_tr.txt
gr_q4_gb-3.anc
gr_q4_gb-3.anc_cdr_st.txt
gr_q4_gb-3.anc_cdr_tr.txt
.
.
gr_q4_gb-4000.anc... (6 Replies)
Discussion started by: sammy777888
6 Replies
3. Shell Programming and Scripting
Hi,
I need a script/command to list out all the files in current path and also the files in folder and subfolders.
Ex: My files are like below
$ ls -lrt
total 8
-rw-r--r-- 1 abc users 419 May 25 10:27 abcd.xml
drwxr-xr-x 3 abc users 4096 May 25 10:28 TEST
$
Under TEST, there are... (2 Replies)
Discussion started by: divya bandipotu
2 Replies
4. UNIX for Dummies Questions & Answers
Hi,
I am trying to print a listing of files from the top level directory, check to see if any files have the same name as the top level directory name and if so, cd to that file and list the files under it. Don't know how to check for the file in the next level.
What I have so far:
... (6 Replies)
Discussion started by: tes218
6 Replies
5. Homework & Coursework Questions
Hello, I tried to count all unique words of all files in one folder and its subfolders. Can anybody say me, why this doesnt work:
ls| find -d | cat | tr "\ " "\n"| uniq -u | wc -l
???
Cat writes only the names of those files, but not the wors, which should be in them.
Thanks for any advice.
... (9 Replies)
Discussion started by: Dworza
9 Replies
6. UNIX for Dummies Questions & Answers
First of all, the extent of my unix knowledge is next to nil. I've been able to telnet to a unix box, and thanks to the Computer Hope website, I've been able to learn a few basic commands to navigate from folder to folder, and view contents.
What I really need to do is obtain a count of all... (2 Replies)
Discussion started by: scarfinv
2 Replies
7. UNIX for Dummies Questions & Answers
Dear UNIX-Community,
can help me doing 2 things in Debian 5.0?
1.) Create 100 folders
Format: ./0/0, ./0/1, ./0/2, ...,./0/9, ./1/0/, ..., ./9/9
2.) Move over 200.000 files into the subdirectories according to their last digits.
12398123.dat -> ./3/2/12398123.dat
48161.dat ->... (2 Replies)
Discussion started by: diadas
2 Replies
8. Shell Programming and Scripting
Hi, Dear all:
One question ! ^_^
I'm using bash under Ubuntu 9.10.
My question is not to rename all ".JPG" files to ".jpg" in a single folder, but to rename all ".JPG" files to ".jpg" in all subfolders.
To rename all ".JPG" to ".jpg" in a single folder,
for x in *.JPG; do mv "$x"... (7 Replies)
Discussion started by: jiapei100
7 Replies
9. Shell Programming and Scripting
i need to change string in all files in current folder and all subfolders. i wrote the following script. It works good except it dont delete temp file from subfolders.
for z in `find . -type f -name "*.html" -o -name "*.htm"`; do
sed -e 's@abc@xyz@g' $z>temp;
mv temp $z;
done
any idea?... (1 Reply)
Discussion started by: crazynups
1 Replies
10. UNIX for Dummies Questions & Answers
Hi ALL
I would like know how many files there under a particular folder, which contains subfolders.
Thanks (5 Replies)
Discussion started by: cy163
5 Replies
PEGASUS-EXITCODE(1) PEGASUS-EXITCODE(1)
NAME
pegasus-exitcode - Checks the stdout/stderr files of a workflow job for any indication that an error occurred in the job. This script is
intended to be invoked automatically by DAGMan as the POST script of a job.
SYNOPSIS
pegasus-exitcode [-h][-t n][-r rv][-n] job.out
DESCRIPTION
pegasus-exitcode is a utility that examines the STDOUT of a job to determine if the job failed, and renames the STDOUT and STDERR files of
a job to preserve them in case the job is retried.
Pegasus uses pegasus-exitcode as the DAGMan postscript for all jobs submitted via Globus GRAM. This tool exists as a workaround to a known
problem with Globus where the exitcodes of GRAM jobs are not returned. This is a problem because Pegasus uses the exitcode of a job to
determine if the job failed or not.
In order to get around the exitcode problem, Pegasus wraps all GRAM jobs with Kickstart, which records the exitcode of the job in an XML
invocation record, which it writes to the job's STDOUT. The STDOUT is transferred from the execution host back to the submit host when the
job terminates. After the job terminates, DAGMan runs the job's postscript, which Pegasus sets to be pegasus-exitcode. pegasus-exitcode
looks at the invocation record generated by kickstart to see if the job succeeded or failed. If the invocation record indicates a failure,
then pegasus-exitcode returns a non-zero result, which indicates to DAGMan that the job has failed. If the invocation record indicates that
the job succeeded, then pegasus-exitcode returns 0, which tells DAGMan that the job succeeded.
pegasus-exitcode performs several checks to determine whether a job failed or not. These checks include:
1. Is STDOUT empty? If it is empty, then the job failed.
2. Are there any <status> tags with a non-zero value? If there are, then the job failed. Note that, if this is a clustered job, there
could be multiple <status> tags, one for each task. If any of them are non-zero, then the job failed.
3. Is there at least one <status> tag with a zero value? There must be at least one successful invocation or the job has failed.
In addition, pegasus-exitcode allows the caller to specify the exitcode returned by Condor using the --return argument. This can be passed
to pegasus-exitcode in a DAGMan post script by using the $RETURN variable. If this value is non-zero, then pegasus-exitcode returns a
non-zero result before performing any other checks. For GRAM jobs, the value of $RETURN will always be 0 regardless of whether the job
failed or not.
Also, pegasus-exitcode allows the caller to specify the number of successful tasks it should see using the --tasks argument. If
pegasus-exitcode does not see N successful tasks, where N is set by --tasks, then it will return a non-zero result. The default value is 1.
This can be used to detect failures in clustered jobs where, for any number of reasons, invocation records do not get generated for all the
tasks in the clustered job.
In addition to checking the success/failure of a job, pegasus-exitcode also renames the STDOUT and STDERR files of the job so that if the
job is retried, the STDOUT and STDERR of the previous run are not lost. It does this by appending a sequence number to the end of the
files. For example, if the STDOUT file is called "job.out", then the first time the job is run pegasus-exitcode will rename the file
"job.out.000". If the job is run again, then pegasus-exitcode sees that "job.out.000" already exists and renames the file "job.out.001". It
will continue to rename the file by incrementing the sequence number every time the job is executed.
OPTIONS
-h, --help
Prints a usage summary with all the available command-line options.
-t n, --tasks n
Number of tasks expected. If less than n tasks succeeded, then pegasus-exitcode will fail with a non-zero return value. This is used in
cases where we may not get a Kickstart invocation record for some tasks. Normally Seqexec will detect failed Kickstart invocations and
fail accordingly.
-r rv, --return rv
Return value reported by DAGMan. This can be specified in the DAG using the $RETURN variable. If this is non-zero, then
pegasus-exitcode immediately fails with a non-zero return value itself.
-n, --no-rename
Don't rename job.out and job.err to .out.XXX and .err.XXX. This option is used primarily for testing.
AUTHORS
Gideon Juve <juve@usc.edu>
Pegasus Team http://pegasus.isi.edu
05/24/2012 PEGASUS-EXITCODE(1)