03-04-2005
Scripting Best Practices
Hi - I am new to this and was wondering if some of you can help me out. I am just starting to write scripts and need some guidelines on creating scripts. I'm calling them "Best Practices"...what should I do and not do when creating scripts.
All I know so far is that I should avoid putting usernames/passwords in scripts and I should avoid hard-coding a host name in a script. I would think there are a lot more of things like this, so if you could help me out, I would greatly appreciate it.
Thanks!
Todd
7 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I am new to ksh scripts (still reading manuals). I need to write an application that reads a multi-line parameter file, builds sql on-the-fly, runs plsql and saves the output in a specific format for further processing. I am looking for anything on Best Practices for building such an... (1 Reply)
Discussion started by: mtravis
1 Replies
2. UNIX for Advanced & Expert Users
Has anyone implemented or have suggestions on how to shutdown many remote unix/linux servers from a single script initiated from 1 server?
I need this to execute in parallel as time is not on my side. Our ups is sadly underrated and will die in approximately 15 minutes. (There is not... (10 Replies)
Discussion started by: jsw371
10 Replies
3. Shell Programming and Scripting
I know there is a command called trap which can be used to capture the signals from a shell script and redirect the control to a required function (such as a cleanup).
My question is - Those of you who have written lot of shell scripts - do you always write a set of trap commands to capture... (4 Replies)
Discussion started by: sagar_evc
4 Replies
4. UNIX for Dummies Questions & Answers
Hi all,
i am trying to incorporate source control management in my project. We have about 50 - 60 shell scripts on 3 different machines dev, stag and production, but there is no source control.
All the files have to be located at specific locations on each machine for it to work
I want to... (4 Replies)
Discussion started by: chvs2000
4 Replies
5. Shell Programming and Scripting
Hey there.
I am a relative rookie when it comes to Linux/Unix Administration and have been learning to adapt my meager coding skill to working with shell scripts in the 'nix realms. I have done some exhausting searches for and found plenty of information on making scripts globally available but... (2 Replies)
Discussion started by: Tenuous
2 Replies
6. Solaris
Dear all,
Kinda lame question but i'd like to hear your experiences and advice.
Question in short
-----------------
What permission should a mount point "ideally" have - i think it's root.
Ex:- /usr/app/ i'd set the app to be owned by root and within /usr/app i would create another... (1 Reply)
Discussion started by: ossupport55
1 Replies
7. Linux
Hello admins and gurus
I have a controversial topic: now we are investing in a new Linux OS that will hold our Sybase database. The server will virtualized on a VMware server hosted on SAN storage. Now the question is, when we install the database engine is it better - in terms of performance -... (1 Reply)
Discussion started by: abohmeed
1 Replies
LEARN ABOUT DEBIAN
nautilus-scripts-manager
NAUTILUS-SCRIPTS-MANAGER(1) General Commands Manual NAUTILUS-SCRIPTS-MANAGER(1)
NAME
nautilus-scripts-manager - easy tool for nautilus scripts management
SYNOPSIS
nautilus-scripts-manager [options]
DESCRIPTION
This manual page documents briefly the nautilus-scripts-manager command.
nautilus-scripts-manager is a program that allows any user to easily manage installed Nautilus scripts.
GENERAL OPTIONS
-h, --help
Show summary of options.
-v, --version
Show version of program.
COMMANDS
One (and only one) of the following commands can be passed:
-e, --enable=ENABLE
Enable script ENABLE.
-d, --disable=DISABLE
Disable script DISABLE.
-l, --list-enabled
List enabled scripts.
-a, --list-available
List available scripts.
If no command is provided, the graphical interface is started.
OPTIONS
-e, --position=POSITION
In conjunction with -e or -d: establish the position of the script (can be just a name, or a path with slashes - quote it if it con-
tains spaces).
SEE ALSO
nautilus(1),
AUTHOR
nautilus-scripts-manager and this manual page were written by Pietro Battiston <me@pietrobattiston.it>.
This manual page was written for the Debian project (but may be used by others).
July 14, 2009 NAUTILUS-SCRIPTS-MANAGER(1)