07-17-2014
Dear Corona688,
I first checked with a single operation including other command-line options and then put it into the loop for all the sequences. So far working good
Thanks again.
Regards
This User Gave Thanks to biochemist For This Post:
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I've written a script (bgrep) for a more advanced grep command (& attached a cut down version below). I'm trying allow all grep options to be used, or in any combination.
The script works fine if I type say
bgrep -i -files product
it will return a non-case sensitive list of matches for... (3 Replies)
Discussion started by: Kevin Pryke
3 Replies
2. UNIX for Advanced & Expert Users
Hey guys,
I have an interactive script that is quite critical to our production environmentl thus updating it to run non-interactively is not an option.
The script takes a varying number of arguments, which it ques untill user confirm end of data entry
e.g of user input :
1
2
y ... (3 Replies)
Discussion started by: geek.ksa
3 Replies
3. Shell Programming and Scripting
The following bash script does not work because the java/groovy code always thinks there are four arguments even if there are only 1 or 2. As you can see from my hideous backslashes, I am using cygwin bash on windows.
export... (1 Reply)
Discussion started by: siegfried
1 Replies
4. Shell Programming and Scripting
Hi!
I have a python script that requires arguments and these arguments are file paths. This script works fine when executed like this:
/my_python_script "file_path1" "file_path2"
(i added quotes as some file names may have weird characters)
the issue happens when i launch my python script... (14 Replies)
Discussion started by: gigagigosu
14 Replies
5. Shell Programming and Scripting
I'm pretty new to bash scripting and I've found myself writing things like this (and the same with even more nesting):
if $CATEGORIES; then
if $LABEL_SLOTS; then
$pyth "$wd/texify_grammar.py" "$input" "$texfile" "--label-slots" "--categories" "$CATEGORY_LIST"
... (9 Replies)
Discussion started by: burbly
9 Replies
6. Shell Programming and Scripting
I've tried to find a solution to this, but I"m stumped.
OS - RH Linux 5.9
I have a bash script <myProgram.sh> that gets executed manually and creates a small response file. I'm trying to automate the running of this script.
When myProgram.sh runs, it prompts the user to enter 2 pieces of... (13 Replies)
Discussion started by: progkcp
13 Replies
7. Shell Programming and Scripting
Hi,
I wanted to pass an argument to a bash script. So that the argument is used inside the awk command inside the bash script.
I know the noraml way of passing argument to a bash script as below :
sh myScript.sh abc
Inside the bash script i can use like this
myArg1=$1
wc $myArg
But... (8 Replies)
Discussion started by: shree11
8 Replies
8. Shell Programming and Scripting
I have a script test.sh which reads various inputs from a user.
#!/bin/ksh
read x
read y
read z
echo x: $x y: $y z: $z
# read few more things again
read a
read b
echo a: $a b: $b
When i run this script as
test.sh << EOF
1
2
EOF (3 Replies)
Discussion started by: ariesb2b
3 Replies
9. Shell Programming and Scripting
Hi,
I have a requirement for creating a MQ (queue) where the inputs has to be passed as arguments.
Running the script as below
./hi.sh "Servername" "QueueManagername" "QueuecreationCommand"
cat hi.sh
echo "Welcome to $1"
runmqsc $2 < $3
But the queue creation command is... (9 Replies)
Discussion started by: Anusha M
9 Replies
10. UNIX for Beginners Questions & Answers
I at the moment, making a simple bash script, capable of setting up an workspace for me, so i don't have to do it manually.. Problem is though i can't seem to provide the bash script any argument, without running into my error checks, checking for input...
Here is the code:
#!/bin/bash... (7 Replies)
Discussion started by: kidi
7 Replies
LEARN ABOUT OSF1
rcsmerge
rcsmerge(1) rcsmerge(1)
NAME
rcsmerge - merge RCS revisions
SYNOPSIS
rcsmerge [options] file
OPTIONS
Use subst style keyword substitution. See co(1) for details. For example, -kk -r1.1 -r1.2 ignores differences in keyword values when merg-
ing the changes from 1.1 to 1.2. Send the result to standard output instead of overwriting the working file. Run quietly; do not print
diagnostics. Merge with respect to revision rev. Here an empty rev stands for the latest revision on the default branch, normally the
head. Emulate RCS version n. See co(1) for details. Use suffixes to characterize RCS files. See ci(1) for details.
DESCRIPTION
rcsmerge incorporates the changes between two revisions of an RCS file into the corresponding working file.
Pathnames matching an RCS suffix denote RCS files; all others denote working files. Names are paired as explained in ci(1).
At least one revision must be specified with one of the options described below, usually -r. At most two revisions may be specified. If
only one revision is specified, the latest revision on the default branch (normally the highest branch on the trunk) is assumed for the
second revision. Revisions may be specified numerically or symbolically.
rcsmerge prints a warning if there are overlaps, and delimits the overlapping regions as explained in merge(1). The command is useful for
incorporating changes into a checked-out revision.
EXAMPLES
Suppose you have released revision 2.8 of f.c. Assume furthermore that after you complete an unreleased revision 3.4, you receive updates
to release 2.8 from someone else. To combine the updates to 2.8 and your changes between 2.8 and 3.4, put the updates to 2.8 into file f.c
and execute rcsmerge -p -r2.8 -r3.4f.c >f.merged.c
Then examine f.merged.c. Alternatively, if you want to save the updates to 2.8 in the RCS file, check them in as revision 2.8.1.1 and exe-
cute co -j: ci -r2.8.1.1 f.c co -r3.4 -j2.8:2.8.1.1 f.c
As another example, the following command undoes the changes between revision 2.4 and 2.8 in your currently checked out revision in f.c.
rcsmerge -r2.8 -r2.4 f.c
Note the order of the arguments, and that f.c will be overwritten.
ENVIRONMENT
options prepended to the argument list, separated by spaces. See ci(1) for details.
DIAGNOSTICS
Exit status is 0 for no overlaps, 1 for some overlaps, 2 for trouble.
IDENTIFICATION
Author: Walter F. Tichy.
Revision Number: 1.1.6.2; Release Date: 1993/10/07.
Copyright (C) 1982, 1988, 1989 by Walter F. Tichy.
Copyright (C) 1990, 1991 by Paul Eggert.
SEE ALSO
ci(1), co(1), ident(1), merge(1), rcs(1), rcsdiff(1), rcsintro(1), rlog(1), rcsfile(5)
Walter F. Tichy, RCS--A System for Version Control, Software--Practice & Experience 15, 7 (July 1985), 637-654.
rcsmerge(1)