|
|
Sponsored Content
Top Forums
Shell Programming and Scripting
Run a job between times else run later
Post 302936858 by twinion on Saturday 28th of February 2015 03:08:13 PM
02-28-2015
Hi, thanks for the reply. The system I use is a sun Solaris. The break part was just away of sitting there and waiting for a job to finish, this starts the same time the other job does (8pm) once the other job finishes It creates the trigger file. I get this to wait for it and kick off. I'm doing this the automate several tasks. Someone tried to do it via the cron and it went horribly wrong. You're right about the test, could increase it for sure. I can't put a big delay on it because the job I wait for can take a short time or a long time. So I get it to wait.
As for searching, I love to look around to learn, as I said I'm very new at this scripting lark
I posted here to see others approach. I will continue to look and learn what i can as my approach can be very converluted. Any input positive or negative is help because I can hopefully learn from it.
As for searching, I love to look around to learn, as I said I'm very new at this scripting lark
I posted here to see others approach. I will continue to look and learn what i can as my approach can be very converluted. Any input positive or negative is help because I can hopefully learn from it.|
|
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I have a perl script, when I ran manually it works perfect. I check the permissions which are fine.
How can I find out why it is not running? how can I setup a log to check.
I am running it on solaris 9.
It compares multiple files, SCP and then send out an e-mail.
As I said when I ran it... (2 Replies)
Discussion started by: amir07
2 Replies
2. Programming
I have a dual core pc, I write a application with two child process.
I know I can add sched_get_cpu to know the process run on which core, but, it just when the sched_get_cpu is called, it will tell me the result, my quesion is how to know the child proceess spend how many times on one core. (2 Replies)
Discussion started by: yanglei_fage
2 Replies
3. Shell Programming and Scripting
Hi all,
I have a requirement in which a script invokes a Java program.
Lets say script ABC invokes a java program with cfg file a parameter.
This script takes 10 minutes to execute .
Like this ineed to run the program 10 times meaning 100 minutes if i do it sequentially.
If i open... (2 Replies)
Discussion started by: rahman_riyaz
2 Replies
4. Shell Programming and Scripting
Hi
I'm running a program many times with differents input.
I mean that i run my_prog with some parameters and i wait till the end, then i start again another simulations with some others differents parameters.
Is possible to make it automatic with a script bash.
Maybe i need some... (2 Replies)
Discussion started by: Dedalus
2 Replies
5. Shell Programming and Scripting
Hi,
First i need to cd to this directory $SWDIR/util
Second i need to run the following either 4 times or 20 times
./swadm add_process 1 BG Y
how can i put this in a script which should ask for user input on how many times you want to run this
Thanks, (5 Replies)
Discussion started by: lookinginfo
5 Replies
6. Shell Programming and Scripting
i should use this script runs how many times before ?
how can i do_? (3 Replies)
Discussion started by: utoptas
3 Replies
7. Shell Programming and Scripting
Okay so I've got a command to start my java server up, but I want it to start at say 8:00AM and then stop at 11:00PM. In order to stop it I have to type stop and press enter in the terminal. I've been trying to get this to work and I'm having no luck. Here's my command:
#!/bin/bash
cd "`dirname... (2 Replies)
Discussion started by: JustChillin1414
2 Replies
8. Programming
Hi,
I have a fortran program with serial and MPI version. I want to compare the time taken by these programs to run. I use ifort/gfortran compiler.
How to compare the time taken by each program to run? Is there any sample code for comparison?
Thanks,
rpd (1 Reply)
Discussion started by: rpd25
1 Replies
9. Shell Programming and Scripting
Hi,
Someone please help me to run the script to maintain a Job: Which can be run for every one hour and should maintain the last two hours files only. It should delete the rest of the files in a dir.
Please suggest me with the sample script.
Thanks !!
Reagrds,
Rama (5 Replies)
Discussion started by: ramagore85
5 Replies
10. Solaris
Hi all,
I have this script which sends mail whenever the system is down. It works fine. Normally the system is down from 21 00 to 21 30 from Monday to Saturday and from 21 00 on Sunday to Monday 06 00 for maintenance. So I want the below script to run only when the system is up, i.e outside the... (2 Replies)
Discussion started by: frum
2 Replies
LEARN ABOUT DEBIAN
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)