man at command is working, how can i schedule a job using this. Do you have any tutorial which i could read
The man page should give a lot of insight, at isn't really a reoccurring task like cron is. Are you not happy with cron for some reason? There aren't replacements of it for a very good reason obviously.
hi
i am needed to use tidal's scheduler to schedule unix scripts available on server A. while creating a job to be scheduled, it has an option called command which will take a path of the file. i have seen several examples in the following way
e:\tidal\bin\sleep.exe
here i did not understand two... (0 Replies)
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?... (1 Reply)
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? (3 Replies)
Up until now I used Oracle's Enterprise manager to submit the batch job. However its SMTP function (Sends EMail about Job status) is unstable lately. I want to use Unix's Cron to submit my batch job. This way I can also eliminate the middle layer (Oracle's Enterprise manager). Please help how I can... (1 Reply)
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... (3 Replies)
Hi All,
I have a script which will restart some web server and bring it up again. For that I need to retrieve 3 password from CyberArk (Cyber-Ark - Wikipedia, the free encyclopedia) vault.
My question is:
Is this possible to schedule the script through cron and automatic password... (0 Replies)
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 Replies)
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... (1 Reply)
Good Afternoon,
I have a sh script that the admin added to the cron schedule.
It runs fine when I run it manually...but not when scheduled.
I added the path that is found for my user to the script. Still no luck.
Any ideas what I should look at?
Thanks
Marty (8 Replies)
Discussion started by: MSpeare
8 Replies
LEARN ABOUT OPENSOLARIS
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.11 1 Mar 1994 queuedefs(4)