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
DDB(8) BSD System Manager's Manual DDB(8)
NAME
ddb -- configure DDB kernel debugger properties
SYNOPSIS
ddb capture [-M -core] [-N -system] print
ddb capture [-M -core] [-N -system] status
ddb script scriptname
ddb script scriptname=script
ddb scripts
ddb unscript scriptname
ddb pathname
DESCRIPTION
The ddb utility configures certain aspects of the ddb(4) kernel debugger from user space that are not configured at compile-time or easily
via sysctl(8) MIB entries.
To ease configuration, commands can be put in a file which is processed using ddb as shown in the last synopsis line. An absolute pathname
must be used. The file will be read line by line and applied as arguments to the ddb utility. Whitespace at the beginning of lines will be
ignored as will lines where the first non-whitespace character is '#'.
OUTPUT CAPTURE
The ddb utility can be used to extract the contents of the ddb(4) output capture buffer of the current live kernel, or from the crash dump of
a kernel on disk. The following debugger commands are available from the command line:
capture [-M core] [-N system] print
Print the current contents of the ddb(4) output capture buffer.
capture [-M core] [-N system] status
Print the current status of the ddb(4) output capture buffer.
SCRIPTING
The ddb utility can be used to configure aspects of ddb(4) scripting from user space; scripting support is described in more detail in
ddb(4). Each of the debugger commands is available from the command line:
script scriptname
Print the script named scriptname.
script scriptname=script
Define a script named scriptname. As many scripts contain characters interpreted in special ways by the shell, it is advisable to
enclose script in quotes.
scripts
List currently defined scripts.
unscript scriptname
Delete the script named scriptname.
EXIT STATUS
The ddb utility exits 0 on success, and >0 if an error occurs.
EXAMPLES
The following example defines a script that will execute when the kernel debugger is entered as a result of a break signal:
ddb script kdb.enter.break="show pcpu; bt"
The following example will delete the script:
ddb unscript kdb.enter.break
For further examples, see the ddb(4) and textdump(4) manual pages.
SEE ALSO
ddb(4), textdump(4), sysctl(8)
HISTORY
The ddb utility first appeared in FreeBSD 7.1.
AUTHORS
Robert N M Watson
BUGS
Ideally, ddb would not exist, as all pertinent aspects of ddb(4) could be configured directly via sysctl(8).
BSD
December 24, 2008 BSD