11-08-2011
Quote:
Originally Posted by
nks342
Hi vgersh,
Thanx a lot for the guidance,I am sorry , please explain why to write that pattern inside the single quotes...!!
There's nothing to be sorry about - all you need to think/know is how your script is implemented and why. Doing so will make you more knowledgeable and efficient solving your
own issues.
Please think of how your 'main' script "sources" your config files - this should be enough of a hint for you.
Spend some time and effort on that first...
We're willing to help only the
willing ones.
Good luck!
This User Gave Thanks to vgersh99 For This Post:
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Please Help! :o
I have a main script (ksh) where another script is called (convert_picture). Normally this works ok, but since some changes has been made on the unix-server (I dont know what :( ) suddenly it doesnt work anymore: i get an error message: ksh: convert_picture not found. I am... (3 Replies)
Discussion started by: Rakker
3 Replies
2. UNIX for Dummies Questions & Answers
Hey Guys
from the below script what I understood is we are sending the the first parameter as input to the main (){} file
main > $LOGFILE 2>&1
but can we send two or three parameter as input to this main file as
main > $LOGFILE 2>&1 2>&2 like this
Can any one plz help I need to writ a... (0 Replies)
Discussion started by: pinky
0 Replies
3. Shell Programming and Scripting
Using an awk script , i want to store the value of a variable in the main script.
currently sum is getting reset to blank in the main script.
How to modify the below code to get the value of esum in the variable sum of the main script???
sum=`echo "$row" | awk -F"" '{$esum=$5}'`
... (0 Replies)
Discussion started by: skyineyes
0 Replies
4. UNIX for Advanced & Expert Users
Hi,
I am writing a wrapper script(wrap_script.sh) to one of the main scripts (main_script.sh)
The main script is executed as following:
./main_script.sh <LIST> <STARTDATE> <ENDDATE>
looks for a parameter which is a LIST(consists of different list names that need to be processed), START/END... (0 Replies)
Discussion started by: stunnerz_84
0 Replies
5. Shell Programming and Scripting
Hi,
I am new to shell scripting,and i was planning to write a script that will move files which have a datetime >= currentdate-N from a source to destination folder. All configuration should be done through a properties files.
Here the value of N should be taken as 10 days(modification... (6 Replies)
Discussion started by: rahul125
6 Replies
6. Shell Programming and Scripting
Hi,
I am new to shell scripting,and i was planning to write a script that will FTP files to destination folder.
I was planning that All configuration should be done through a properties files. and finally the output should be
Files are transferred
I have developed a properties file named... (4 Replies)
Discussion started by: rahul125
4 Replies
7. Shell Programming and Scripting
Hi ,
I am new to unix , I was planning to write a ftp script that will transfer the files to the ftp server at the specified
location mention in the properties file.... the structure of the properties file is
configuration for ftp
*********************
#remote url of the machine ... (1 Reply)
Discussion started by: rahul2751
1 Replies
8. Shell Programming and Scripting
Hi All,
I have a script which does report the cpu usuage, there are few output parameter/fields displayed from the script. My problem is I have monitor the output and decide
which cpu number (column 2) has maximum value (column 6).
Since the output is displayed/updated every seconds, it's very... (1 Reply)
Discussion started by: Optimus81
1 Replies
LEARN ABOUT DEBIAN
scriptmgr2
SCRIPTMGR(1) SCRIPTMGR(1)
NAME
scriptmgr - utility for controlling other skytools scripts.
SYNOPSIS
scriptmgr.py [switches] config.ini <command> [-a | job_name ... ]
DESCRIPTION
scriptmgr is used to manage several scripts together. It discovers potential jobs based on config file glob expression. From config file it
gets both job_name and service type (that is the main section name eg [cube_dispatcher]). For each service type there is subsection in the
config how to handle it. Unknown services are ignored.
COMMANDS
status
scriptmgr config.ini status
Show status for all known jobs.
start
scriptmgr config.ini start -a
scriptmgr config.ini start job_name1 job_name2 ...
launch script(s) that are not running.
stop
scriptmgr config.ini stop -a
scriptmgr config.ini stop job_name1 job_name2 ...
stop script(s) that are running.
restart
scriptmgr config.ini restart -a
scriptmgr config.ini restart job_name1 job_name2 ...
restart scripts.
reload
scriptmgr config.ini reload -a
scriptmgr config.ini reload job_name1 job_name2 ...
Send SIGHUP to scripts that are running.
CONFIG
Common configuration parameters
job_name
Name for particulat job the script does. Script will log under this name to logdb/logserver. The name is also used as default for PgQ
consumer name. It should be unique.
pidfile
Location for pid file. If not given, script is disallowed to daemonize.
logfile
Location for log file.
loop_delay
If continuisly running process, how long to sleep after each work loop, in seconds. Default: 1.
connection_lifetime
Close and reconnect older database connections.
log_count
Number of log files to keep. Default: 3
log_size
Max size for one log file. File is rotated if max size is reached. Default: 10485760 (10M)
use_skylog
If set, search for [./skylog.ini, ~/.skylog.ini, /etc/skylog.ini]. If found then the file is used as config file for Pythons logging
module. It allows setting up fully customizable logging setup.
scriptmgr parameters
config_list
List of glob patters for finding config files. Example:
config_list = ~/dbscripts/conf/*.ini, ~/random/conf/*.ini
Service section parameters
cwd
Working directory for script.
args
Arguments to give to script, in addition to -d.
script
Path to script. Unless script is in PATH, full path should be given.
disabled
If this service should be ignored.
Example config file
[scriptmgr]
job_name = scriptmgr_livesrv
logfile = ~/log/%(job_name)s.log
pidfile = ~/pid/%(job_name)s.pid
config_list = ~/scripts/conf/*.ini
# defaults for all service sections
[DEFAULT]
cwd = ~/scripts
[table_dispatcher]
script = table_dispatcher.py
args = -v
[cube_dispatcher]
script = python2.4 cube_dispatcher.py
disabled = 1
[pgqadm]
script = ~/scripts/pgqadm.py
args = ticker
COMMAND LINE SWITCHES
Following switches are common to all skytools.DBScript-based Python programs.
-h, --help
show help message and exit
-q, --quiet
make program silent
-v, --verbose
make program more verbose
-d, --daemon
make program go background
Following switches are used to control already running process. The pidfile is read from config then signal is sent to process id specified
there.
-r, --reload
reload config (send SIGHUP)
-s, --stop
stop program safely (send SIGINT)
-k, --kill
kill program immidiately (send SIGTERM)
Options specific to scriptmgr:
-a, --all
Operate on all non-disabled scripts.
03/13/2012 SCRIPTMGR(1)