Help needed regarding cron job scheduler with CyberArk Password security

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

OS Watcher not running with cron scheduler

Hi team, O.S : Oracle Linux Issue : I am facing issue when running OS watcher script from cron scheduler. But when i run the same command manually, its getting executed. Note : I have to press " Enter " button to get out of the blank screen when I execute the script manually. Below is...

2. Red Hat

Cron scheduler issue

I am trying to schedule a script in Linux to between 8th and the 31st of each month on Sundays @ 6:50 only and i scheduled it as follows: 50 6 8-31 * 0 ksh /home/cpac/SPID_Files/GetFiles.ksh Which did it run on the 8th on Saturday instead of only Sundays !!!

3. UNIX for Advanced & Expert Users

Autosys Scheduler- Running job at particular time

Hi Experts, I am new to Autosys. I created a Autosys box job to run at 10 AM daily. As scheduled, the job starts on time. There is another box job inside the box. I have scheduled it to run at 11 AM but it kicks off automatically with the main job at 10 AM. insert_job: Main-job ...

4. Shell Programming and Scripting

Crontab job scheduler problem

Dear All. I have a scripts which does many task like house keeping, moving file to different location and loading the data into oracle. I run this scripts daliy manually , I decided to put it into cron. I have put the scripts into crantab but the behaviour of the scripts have changed. it...

5. UNIX for Dummies Questions & Answers

CRON JOB SCHEDULER throwing "option not allowed error"

Hi All, Pardon me if this turns out to be a dumb question. But I am trying to schedule a cron job for a my script which takes input options. So an entry in crontab would be something like: 1 * * * * run_report.sh -o out.csv -m monthly -e somename@email.com > cron_output.log 2> cron_error.log...

6. Solaris

CRON Scheduler

I have akorn shell job that I can run manually but when I run via cron it starts and finishes, but does not do what it does when I run it manually. Any ideals on why this is happening?

7. Forum Support Area for Unregistered Users & Account Problems

Help needed on cron job

Hi Yogesh, I have a script where i have set up a cron job. The script is running manually. The cron job is running successfully. The script is written so that whenever the database link is down, we need to get an alert mail. We are getting the mail when we run the script manually but not when...

8. Shell Programming and Scripting

Unix scheduler other than Cron

Do any one know any way of scheduling jobs on Unix without using cron as thats not supported within the company

9. Shell Programming and Scripting

Job scheduler without using cron

Hi, I want to schedule the scripts/batches to run simultaneously. I had all the information in the config (flat)file, which contains script name, time, dependency, path, priority and status etc., I want to run the jobs parellelly and some jobs are required to give the input. How can I do this?...

10. UNIX for Advanced & Expert Users

Job Scheduler Agent-Based.

Hi Gurus, I'm looking for a real Jobs Scheduler Agent-based. My customer is using cron, but need something a little bit clever, where you could configure chain of process ("script x will run if script y is finished", etc). Of course I know solutions like control-M (from BMC...

LEARN ABOUT SUNOS

queuedefs

queuedefs(4)							   File Formats 						      queuedefs(4)

NAME

       queuedefs - queue description file for at, batch, and cron

SYNOPSIS

       /etc/cron.d/queuedefs

DESCRIPTION

       The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue.
       The format of the lines are as follows:

	      q.[njobj][nicen][nwaitw]

       The fields in this line are:

       q	The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs  started  by  batch  (see
		at(1)); c is the default queue for jobs run from a crontab(1) file.

       njob	The  maximum  number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first
		njob jobs will be run, and the others will be run as jobs that are currently running terminate.  The default value is  100.

       nice	The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user.  The default value is 2.

       nwait	The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in  that  job's
		queue, or because the system-wide limit of jobs executing has been reached.  The default value is 60.

       Lines beginning with # are comments, and are ignored.

EXAMPLES

       Example 1: A sample file.

       #
       #
       a.4j1n
       b.2j2n90w

       This  file  specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value
       of 1.  As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before  trying
       again to run it.

       The  b  queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2.  If a job
       cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All	other  queues  can
       have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs
       are running cron will wait 60 seconds before trying again to run it.

FILES

       /etc/cron.d/queuedefs	       queue description file for  at, batch, and  cron.

SEE ALSO

       at(1), crontab(1), nice(1), cron(1M)

SunOS 5.10							    1 Mar 1994							      queuedefs(4)

Shell Programming and Scripting