10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I am very new to Autosys and want to execute my first batch or job there.
I have url to open Autosys and have access of Folder Structure
1. for AutoSys Job log
2. for AutoSys profile and parameters
3. for Shell Scripts
Please share some information that how to create a job using GUI.
I am... (2 Replies)
Discussion started by: Muneshshar
2 Replies
2. UNIX for Advanced & Expert Users
From where i can get complete Ref. pdf of AutoSys r11.3 any one got idea ?
I cant find good document for that (2 Replies)
Discussion started by: ujjwal2120
2 Replies
3. OS X (Apple)
We have a primary and shadow running our scheduler. We need to
upgrade both to a more current OS. We'd like to take down the shadow
and update it, then allow it to become the primary while we update the
current primary. Does Autosys care what OS you are running or can it
potentially toggle... (0 Replies)
Discussion started by: Cjw_55106
0 Replies
4. UNIX for Dummies Questions & Answers
All the autosys jobs are on server-1 and server-1 has been crashed due to some reason, Now I have to run 5 autosys jobs on server-2 (failover server) which are on server 1.
How to do with Autosys command (which command needs to fired on JIL) (0 Replies)
Discussion started by: tp2115
0 Replies
5. UNIX for Dummies Questions & Answers
Guys, anyone familiar with Unix AutoSys?
I am wondering what is done to make a script located in this dir:
/home/user2/mywork.pl
I have access to jil files incase that helps.
to work everyday at 5pm?
Any insight or guidance would be appreciated. (7 Replies)
Discussion started by: DallasT
7 Replies
6. Shell Programming and Scripting
Hi,
I have heard of file watcher job and command job in autosys.
can anyone tell me about box type job?
An example would be appreciated.
Thanks in Advance. (4 Replies)
Discussion started by: diehard
4 Replies
7. Shell Programming and Scripting
Hi,
I need to schedule a script to run at 12:00 on first day of every month.
I don't know how to set it. Like days_of_week, do we have days_of_month where we can put 1?
Thanks,
Siba (5 Replies)
Discussion started by: siba.s.nayak
5 Replies
8. Shell Programming and Scripting
I am not sure why my output keeps going to my std_out_file!!
Here's my JIL:
insert_job: test_autosys job_type: c
command: $SCRIPT_DIR/test
machine: abcde
owner: bob@abcde
permission: gx,wx
date_conditions: 1
days_of_week: mo, tu, we, th, fr
start_times: "8:00, 9:00, 10:00, 11:00,... (4 Replies)
Discussion started by: arex876
4 Replies
9. UNIX for Advanced & Expert Users
I have installed CA::Autosys my pc. It is in /usr/lib/perl5/site_perl/5.8.8/CA/AutoSys/AutoSys.pm .
I have Sybase Installed.
Kindly help to how to connect autosys to database..
Also how do I create users in Autosys..
Please guide me..
Thank You.. (1 Reply)
Discussion started by: bhuvaneshlal
1 Replies
10. UNIX for Advanced & Expert Users
My project uses Autosys.
I am new to this product and I don't know where to start from.
Q1. Please provide me the link where I can get Autosys documentation
Q2. Please refer a good book on Autosys. (Beginner/Intermediate Level) (0 Replies)
Discussion started by: gram77
0 Replies
DH_INSTALLINIT(1) Debhelper DH_INSTALLINIT(1)
NAME
dh_installinit - install upstart jobs or init scripts into package build directories
SYNOPSIS
dh_installinit [debhelperoptions] [--name=name] [-n] [-R] [-r] [-d] [-O] [--params]
DESCRIPTION
dh_installinit is a debhelper program that is responsible for installing upstart job files or init scripts with associated defaults files
into package build directories, and in the former case providing compatibility handling for non-upstart systems.
It also automatically generates the postinst and postrm and prerm commands needed to set up the symlinks in /etc/rc*.d/ and to start and
stop the init scripts.
FILES
debian/package.upstart
If this exists, it is installed into etc/init/package.conf in the package build directory.
debian/package.init
Otherwise, if this exists, it is installed into etc/init.d/package in the package build directory.
debian/package.default
If this exists, it is installed into etc/default/package in the package build directory.
OPTIONS
-n, --noscripts
Do not modify postinst/postrm/prerm scripts.
-o, --onlyscripts
Only modify postinst/postrm/prerm scripts, do not actually install any init script, default files, or upstart job. May be useful if the
init script or upstart job is shipped and/or installed by upstream in a way that doesn't make it easy to let dh_installinit find it.
If no upstart job file is installed in the target directory when dh_installinit --onlyscripts is called, this program will assume that
an init script is being installed and not provide the compatibility symlinks or upstart dependencies.
-R, --restart-after-upgrade
Do not stop the init script until after the package upgrade has been completed. This is different than the default behavior, which
stops the script in the prerm, and starts it again in the postinst.
This can be useful for daemons that should not have a possibly long downtime during upgrade. But you should make sure that the daemon
will not get confused by the package being upgraded while it's running before using this option.
-r, --no-restart-on-upgrade
Do not stop init script on upgrade.
--no-start
Do not start the init script on install or upgrade, or stop it on removal. Only call update-rc.d. Useful for rcS scripts.
-d, --remove-d
Remove trailing d from the name of the package, and use the result for the filename the upstart job file is installed as in etc/init/ ,
or for the filename the init script is installed as in etc/init.d and the default file is installed as in etc/default/ . This may be
useful for daemons with names ending in d. (Note: this takes precedence over the --init-script parameter described below.)
-uparams --update-rcd-params=params
-- params
Pass params to update-rc.d(8). If not specified, defaults will be passed to update-rc.d(8).
--name=name
Install the upstart job file or the init script (and default file) using the filename name instead of the default filename, which is
the package name. When this parameter is used, dh_installinit looks for and installs files named debian/package.name.upstart,
debian/package.name.init and debian/package.name.default, instead of the usual debian/package.upstart, debian/package.init and
debian/package.default.
--init-script=scriptname
Use scriptname as the filename the init script is installed as in etc/init.d/ (and also use it as the filename for the defaults file,
if it is installed). If you use this parameter, dh_installinit will look to see if a file in the debian/ directory exists that looks
like package.scriptname and if so will install it as the init script in preference to the files it normally installs.
This parameter is deprecated, use the --name parameter instead. This parameter will be ignored completely for upstart jobs.
--upstart-only
Only install an upstart job file, and do not include maintainer script code to replace an init script with that upstart job.
This parameter is intended for use when the "package.upstart" file is new and only to be used on Upstart-based systems.
--error-handler=function
Call the named shell function if running the init script fails. The function should be provided in the prerm and postinst scripts,
before the #DEBHELPER# token.
NOTES
Note that this command is not idempotent. dh_prep(1) should be called between invocations of this command. Otherwise, it may cause multiple
instances of the same text to be added to maintainer scripts.
SEE ALSO
debhelper(7)
This program is a part of debhelper.
AUTHORS
Joey Hess <joeyh@debian.org>
Steve Langasek <steve.langasek@canonical.com>
Scott James Remnant <scott@canonical.com>
8.9.0ubuntu2.1 2012-06-12 DH_INSTALLINIT(1)