Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Stop Writing Scripts
The Lounge What is on Your Mind? Stop Writing Scripts Post 302866923 by mikemazz on Wednesday 23rd of October 2013 12:46:25 AM
Old 10-23-2013
Stop Writing Scripts
Please, I beg you, “Stop!” Yes, stop writing scripts and instead build workflows.
Programmers, Sys-Admins, System Support, I'm talking to you.

Ok, I know in this community I'm going to get some serious backlash for my statements but I truly believe in my statement.

There was a time when writing scripts to help support IT infrastructures and changing business processes was the best option. That time is gone. Todays computing systems are rapidly growing in complexity and the need for easier integration and better automation to manage these systems is becoming paramount.

“So where do we go from scripts”?, you ask. “That is the right question”, making reference back to the movie “iRobot”.

I believe the answer is workflow and workflow automation. I don't think this is the right forum to share all the reasons for my answer so let me take another approach and talk about why script fail.

If you are an IT professional, you most certainly have written a script or two in your time. Scripts are written to automate tasks with the general objective to be more productive and reduce errors. In the early stages of an organization or while its environment is small, writing a few scripts seems to add benefit and meet its objectives. However, over time the environment changes, grows and becomes more complex. This results in more tasks, which in turn requires the need to write more scripts. Soon, the ability to manage these scripts themselves becomes overwhelming - welcome to script hell.

AND...

To put it briefly scripts:

1) Have little or no security
2) Lack of reuse
3) Not cross-platform
4) Hard to maintain
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Help on writing scripts!!??

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

writing schell scripts

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

Start and stop of an application thru shell scripts.

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

writing scripts

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

Stopping Start/Stop scripts in reverse order

#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

Services Start & stop scripts--help required

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

HACMP version 5.4 startup and stop scripts

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

[HA] Red Hat 7, pacemaker and start/stop scripts

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

Linux startup and stop scripts using SSH

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

Stop root from writing to directory

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

service

SERVICE(8)                                                    System Manager's Manual                                                   SERVICE(8)

NAME

       service - run a System V init script

SYNOPSIS

       service SCRIPT COMMAND [OPTIONS]

       service --status-all

       service --help | -h | --version

DESCRIPTION

       service  runs  a System V init script or systemd unit in as predictable an environment as possible, removing most environment variables and
       with the current working directory set to /.

       The SCRIPT parameter specifies a System V init script, located in /etc/init.d/SCRIPT, or the name of a systemd unit.  The  existence  of  a
       systemd unit of the same name as a script in /etc/init.d will cause the unit to take precedence over the init.d script.  The supported val-
       ues of COMMAND depend on the invoked script. service passes COMMAND  and OPTIONS to the init script unmodified. For systemd  units,  start,
       stop, status, and reload are passed through to their systemctl/initctl equivalents.

       All scripts should support at least the start and stop commands.  As a special case, if COMMAND is --full-restart, the script is run twice,
       first with the stop command, then with the start command.

       service --status-all runs all init scripts, in alphabetical order, with the status command. The status is [ + ] for running services, [ - ]
       for stopped services and [ ? ] for services without a status command.  This option only calls status for sysvinit jobs.

EXIT CODES

       service calls the init script and returns the status returned by it.

FILES

       /etc/init.d
              The directory containing System V init scripts.

       /{lib,run,etc}/systemd/system
              The directories containing systemd units.

ENVIRONMENT

       LANG,  LANGUAGE,  LC_CTYPE, LC_NUMERIC, LC_TIME, LC_COLLATE, LC_MONETARY, LC_MESSAGES, LC_PAPER, LC_NAME, LC_ADDRESS, LC_TELEPHONE, LC_MEA-
       SUREMENT, LC_IDENTIFICATION, LC_ALL, TERM, PATH
              The only environment variables passed to the init scripts.

SEE ALSO

       /etc/init.d/skeleton
       update-rc.d(8)
       init(8)
       invoke-rc.d(8)
       systemctl(1)

AUTHOR

       Miloslav Trmac <mitr@redhat.com>, Petter Reinholdtsen <pere@hungry.com>

       Licence: GNU Public Licence v2 (GPLv2)

COPYRIGHT

       2006 Red Hat, Inc.,  Petter Reinholdtsen <pere@hungry.com>

Jan 206                                                                                                                                 SERVICE(8)
All times are GMT -4. The time now is 12:03 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy