10-23-2013
Telling us to stop writing scripts is silly. There is "script hell" and then there is "architecture hell", when well-meaning environment designers deny you the ability to use something they think you don't need. Take away the shell and your users are forced to invent silly ways to hack it back in.
Control methods are always useful of course. What about existing, common workflow languages like make ? Much-abused, but at its core, uses very simple "destination:source" rules which I think can be used simply and effectively for lots of things.
Last edited by Corona688; 10-23-2013 at 12:28 PM..
This User Gave Thanks to Corona688 For This Post:
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 CENTOS
sieveshell
SIEVESHELL(1) User Contributed Perl Documentation SIEVESHELL(1)
NAME
sieveshell - remotely manipulate sieve scripts
SYNOPSIS
sieveshell [--user=user] [--authname=authname] [--realm=realm] [--exec=script] server[:port]
sieveshell --help
DESCRIPTION
sieveshell allows users to manipulate their scripts on a remote server. It works via MANAGESIEVE, a work in progress.
The following commands are recognized:
list list scripts on server.
put <filename> upload script to server.
get <name> [<filename>] get script. if no filename display to stdout
delete <name> delete script.
activate <name> activate script.
deactivate deactivate all scripts.
OPTIONS
-u user, --user=user
The authorization name to request; by default, derived from the authentication credentials.
-a authname, --authname=authname
The user to use for authentication (defaults to current user).
-r realm, --realm=realm
The realm to attempt authentication in.
-e script, --exec=script
Instead of working interactively, run commands from script, and exit when done.
REFERENCES
[MANAGESIEVE] Martin, T.; "A Protocol for Remotely Managing Sieve Scripts", draft-ietf-managesieve-03.txt, Mirapoint, Inc.; May 2001, work
in progress.
AUTHOR
Tim Martin <tmartin@mirapoint.com>, and the rest of the Cyrus team <cyrus-bugs@andrew.cmu.edu>.
perl v5.16.3 2014-06-10 SIEVESHELL(1)