10-23-2013
Quote:
1) Have little or no security
2) Lack of reuse
3) Not cross-platform
4) Hard to maintain
Will depend of the quality of the writing...and the person's knowledge and experience
For a company's point of vue, you get what you pay for... A truly experienced UNIX sysadmin script will not look the same as the one writen by a "highly qualified" IT consultant that left IT college 3 years ago with a 6 month shell class ...
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 DEBIAN
sysadmin
SYSADMIN(1) General Commands Manual SYSADMIN(1)
NAME
sysadmin - responsible for everything imaginable that may or may not have to do with the system you're using. Contraction of "system" and
"administrator"
SYNOPSIS
sysadmin [-ab] [-cd] [-ef] etc......
DESCRIPTION
sysadmin takes care of everything, is generally harangued, must be supplied with coffee, chocolate, and alcohol in order to function prop-
erly, cannot be exposed to direct sunlight, and must not be allowed to have a life.
sysadmin is not intended as a user interface routine; other programs provide user-friendly front ends; sysadmin is used by everyone who can
track him [her] down.
With no flags, sysadmin reads its standard input up to an EOF, or a line which sysadmin wishes to parse, and then proceeds to ignore it
entirely and read news all day. When invoked with the -w option, sysadmin reads standard input and responds according to terms of job
description.
OPTIONS
-bofh Go into Bastard Operator From Hell mode. This option causes sysadmin to use tools stored in the /usr/lib/bofh directory to parse
the standard input and route user tasks appropriately.
-cd causes sysadmin to become caffeine-deprived, resulting in system slowdowns.
-b causes the sysadmin to function normally while augmenting the standard input with beer(5). Can be used with the -t option as well,
depending upon which version of sysadmin you are running.
-t causes the sysadmin to smoke tobacco, which can result in significant performance improvement, provided you are running the correct
version of sysadmin.
-Cfile Specify an alternate configuration file (sysadmin.cf is the standard).
-dX set debuggin value to X.
-fFullname
Set the full name of the sysadmin.
-Bf Create the sysadmin.cf configuration freeze file.
-lname Sets the name of the "luser" person (that is, originator of a given request). -l can only be used by "trusted" users (who are listed
in sysadmin.cf).
NOTES
The -t option should not be used with a version of sysadmin which is not capable of parsing tobacco input. Though the functionality of
this command may seem similar to the -b option, it should not be confused with that or the related -c option.
25 September 1995 SYSADMIN(1)