10-23-2013
Quote:
Originally Posted by
wisecracker
I, as a complete novice, am wondering why is shell scripting considered _complete_hell_ from your POV...
I suspect it's not to do with the shell scripting itself but the management of it. "There's a bunch of script files on server x left by admin z, nobody knows what they do" kind of thing.
Which doesn't make shell scripting the problem as much as the lack of documentation...
Somehow making it all visual doesn't strike me as actually solving it. Whether it's text or diagrams, you have to know the tools.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello,
I don't know anything about scripting, and I want help on writing a script, which can help me doing my research.
Actually I have some ASCII format files formatted in a way looks like this
6 lines of text that is not important for me
File_header_name_number_1 <--... (1 Reply)
Discussion started by: geoquest
1 Replies
2. Shell Programming and Scripting
I am very new to Unix. I need to write a script that will grep some files, etc. When I write the script, do I need to know what shell I am using? If so, how do I do that? (1 Reply)
Discussion started by: ssmiths001
1 Replies
3. Shell Programming and Scripting
Hi,
I just learnt the shell scripting and got working on that right now. I have one problem.
Here i am having a java application that needs to be start and stop using two shell scripts, i.e., starting the java application using one shell script and stopping the application using another... (1 Reply)
Discussion started by: sadha
1 Replies
4. Shell Programming and Scripting
What would happen if I didn't use "./" before writing a script? (4 Replies)
Discussion started by: ebethea27703
4 Replies
5. Shell Programming and Scripting
#Define the Start/Stop/Status Scripts to include
SSS_SCRIPTS=( prog1 prog2 prog3 etc...... )
#Start the scripts
StartScripts()
{
for SSS in ${SSS_SCRIPTS}
do
./$SSS start
done
}
#Stop the Scripts
StopScripts()
{
for SSS in ${SSS_SCRIPTS}
do
./$SSS stop #<---I... (1 Reply)
Discussion started by: madasafish
1 Replies
6. Shell Programming and Scripting
Dear All,
Pls find my scripts for Agent services strat & stop.
EAMSROOT=/opt/panaces
export EAMSROOT
cd $EAMSROOT
nohup ./OracleAgent.sh start &
nohup ./PFRAgent.sh start &
nohup ./PFR.sh start &
nohup ./SolarisOSAgent.sh start &
exit 0
EAMSROOT=/opt/panaces
export EAMSROOT
cd... (0 Replies)
Discussion started by: starnaresh
0 Replies
7. AIX
Hi
My hacmp version is 5.4 and it is a active passive cluster.
Where can I find the startup and stop scripts?
Please assist. Thanks. (2 Replies)
Discussion started by: samsungsamsung
2 Replies
8. Red Hat
Hi there,
I am wondering if I could add start/stop ksh scripts provided by 3rd party to cluster... I read that script must be ocf/lsb compliant, however, in AIX I can just set up two separate scripts for starting and stopping application. Can similar be done under RH Linux cluster?
Cheers,
c (1 Reply)
Discussion started by: cyjan
1 Replies
9. Shell Programming and Scripting
I have a question. Actually I want to make two scripts, one is startup.sh and other is stopscript.sh
so for example, I have 5 servers.
Each server has two instances :-
abc111 - Masters
-cra4
abc222 -middle tear
-cra
abc333 -middle tear
-cra1
abc444 -middle tear
... (1 Reply)
Discussion started by: siddharthjain
1 Replies
10. UNIX for Advanced & Expert Users
Is there a way to stop root from writing to a directory? I already tried chattr but that did not seem to work.
chattr +i directory (12 Replies)
Discussion started by: cokedude
12 Replies
LEARN ABOUT MOJAVE
jrunscript
jrunscript(1) General Commands Manual jrunscript(1)
NAME
jrunscript - command line script shell
SYNOPSIS
jrunscript [ options ] [ arguments... ]
PARAMETERS
options
Options, if used, should follow immediately after the command name.
arguments
Arguments, if used, should follow immediately after options or command name.
DESCRIPTION
jrunscript is a command line script shell. jrunscript supports both an interactive (read-eval-print) mode and a batch (-f option) mode of
script execution. This is a scripting language independent shell. By default, JavaScript is the language used, but the -l option can be
used to specify a different language. Through Java to scripting language communication, jrunscript supports "exploratory programming"
style.
NOTE: This tool is experimental and may not be available in future versions of the JDK.
OPTIONS
-classpath path
Specify where to find the user's .class files that are accessed by the script.
-cp path
This is a synonym for -classpath path
-Dname=value
Set a Java system property.
-Jflag
Pass flag directly to the Java virtual machine on which jrunscript is run.
-l language
Use the specified scripting language. By default, JavaScript is used. Note that to use other scripting languages, you also need to spec-
ify the corresponding script engine's jar file using -cp or -classpath option.
-e script
Evaluate the given script. This option can be used to run "one liner" scripts specified completely on the command line.
-encoding encoding
Specify the character encoding used while reading script files.
-f script-file
Evaluate the given script file (batch mode).
-f -
Read and evaluate a script from standard input (interactive mode).
-help
Output help message and exit.
-?
Output help message and exit.
-q
List all script engines available and exit.
ARGUMENTS
If [arguments...] are present and if no -e or -f option is used, then the first argument is the script file and the rest of the arguments,
if any, are passed as script arguments. If [arguments..] and -e or -f option are used, then all [arguments..] are passed as script argu-
ments. If [arguments..], -e and -f are missing, interactive mode is used. Script arguments are available to a script in an engine variable
named "arguments" of type String array.
EXAMPLES
Executing inline scripts
jrunscript -e "print('hello world')"
jrunscript -e "cat('http://java.sun.com')"
Use specified language and evaluate given script file
jrunscript -l js -f test.js
Interactive mode
jrunscript
js>print('hello world');
hello world
js>34 + 55
89
js> thread(function() { print('hello world'); }
hello world
js>
Run script file with script arguments
jrunscript test.js arg1 arg2 arg3
test.js is script file to execute and arg1, arg2 and arg3 are passed to script as script arguments. Script can access these using "argu-
ments" array.
SEE ALSO
If JavaScript is used, then before evaluating any user defined script, jrunscript initializes certain built-in functions and objects. These
JavaScript built-ins are documented in jsdocs.
06 Aug 2006 jrunscript(1)