Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

scriptmgr2(1) [debian man page]

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)

Check Out this Related Man Page

LONDISTE(5)															       LONDISTE(5)

NAME

       londiste - PostgreSQL replication engine written in python

SYNOPSIS

       [londiste]
       job_name = asd

DESCRIPTION

       The londiste configuration file follow the famous .INI syntax. It contains only one section named londiste.

       Most defaults values are reasonable ones. That means you can only edit provider_db, subscriber_db and pgq_queue_name and be done with
       londiste configuration.

OPTIONS

       You can configure the following options into the londiste section.

       job_name
	   Each Skytools daemon process must have a unique job_name. Londiste uses it also as consumer name when subscribing to queue.

       provider_db
	   Provider database connection string (DSN).

       subscriber_db
	   Subscriber database connection string (DSN).

       pgq_queue_name
	   Name of the queue to read from. Several subscribers can read from same queue.

       logfile
	   Where to log londiste activity.

       pidfile
	   Where to store the pid of the main londiste process, the replay one.

       lock_timeout
	   Few operations take lock on provider (provider add/remove, compare, repair). This parameter specifies timeout in seconds (float) how
	   long a lock can be held. New in version 2.1.8. Default: 10

       loop_delay
	   How often to poll events from provider. In seconds (float). Default: 1.

       pgq_lazy_fetch
	   How many events to fetch at a time when processing a batch. Useful when you know a single transaction (maintenance UPDATE command,
	   e.g.) will produce a lot of events in a single batch. When lazily fetching, a cursor is used so as to still process a single batch in a
	   single transaction. Default: 0, always fetch all events of the batch, not using a cursor.

       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. Default: 0

EXAMPLE

	   [londiste]
	   job_name = test_to_subcriber

	   provider_db = dbname=provider port=6000 host=127.0.0.1
	   subscriber_db = dbname=subscriber port=6000 host=127.0.0.1

	   # it will be used as sql ident so no dots/spaces
	   pgq_queue_name = londiste.replika

	   logfile = /tmp/%(job_name)s.log
	   pidfile = /tmp/%(job_name)s.pid

SEE ALSO

       londiste(1)

								    03/13/2012							       LONDISTE(5)
Man Page