Dear all,
I have to create a shell script which will run the job during weekday/weekend in following manner: -
There are 3 jobs
These jobs changes its flag to "COMPLETED" in below 2 ways
1. These 3 jobs which runs after the completion of previous one i.e JB_1 runs and changes its flag to "COMPLETED" then only the next job gets started.
2. The second way to change the jobs status to "COMPLETED" without running it with the following command: -
Now my concern is how should i create a shell script to do the above activities during weekday and weekend as mentioned below.
During weekday (Monday to friday) these jobs should simply change its flag to COMPLETED as mentioned in point 2.
During weekend (Saturday and Sunday) these job should run and then changes its flag to COMPLETED as mentioned in Point 1.
What these jobs internally does is irrelevant.
HI,
I need to schedule a no.of jobs using the cron facility.
I currently do two kinds of scheduling,one based on the database load(after the database is loaded the program will start) and the other is based on time.....(say 10.00a.m daily)
the problem is..........
When the database is loaded... (1 Reply)
Hi,
I need to schedule a shell script which executes another shell script along with a series of other commands.
When the inner shell script is executed it prompts for a password.....
This inner shell cannot be changed
How can I do this????
Regards,
Chaitrali. (4 Replies)
Hi all,
Please help me with the issue im facing.
my client has a recquirement that unix script has to schedule the no.of jobs based on the value from the oracle table.for example if the table has a value of 20 the unix script has to schedule 20 jobs.im able to write the script to get the value... (1 Reply)
Status quo is, within a web application, which is coded completely in php (not by me, I dont know php), I have to fill out several fields, and execute it manually by clicking the "go" button in my browser, several times a day.
Thats because:
The script itself pulls data (textfiles) from a... (3 Replies)
shell=ksh,
How could I schedule tasks in shell script INSTEAD OF using the crontab -e functionality?
For example, I want a script to print "Hello World" every 10 seconds (i.e., INTERVAL = 10s) until external termination signal is triggered.
Thanks, (2 Replies)
Hi All,
How to schedule a shell script(script name- byweeklyreport.sh) it should run by weekly in corn job or is there any script have to write to check week and then run the above script.
example-1st run March 06 2013
2nd run March 20 2013
3rd run April 3 2013... (13 Replies)
Hi All,
I have a script that I need to schedule on daily basis. How can I schedule a script in centos. Like I want to run that script evryday at 10 AM and can I store the output of the script in a log file.
Thanks
---------- Post updated 04-18-14 at 12:52 AM ---------- Previous update... (0 Replies)
I have multiple jobs and each job dependent on other job.
Each Job generates a log and If job completed successfully log file end's with JOB ENDED SUCCESSFULLY message and if it failed then it will end with JOB ENDED with FAILURE.
I need an help how to start.
Attaching the JOB dependency... (3 Replies)
HI Guys
I need one shell script to be scheduled to run one shell script to be executed automatically every Wednesday at 10 AM Without crontab and "at" command..
Could you provide your suggestions ?
Thanks and Regards
kshitij Kulshreshtha (6 Replies)
Discussion started by: kshitij
6 Replies
LEARN ABOUT SUSE
vm-install-jobs
vm-install-jobs(8) System Manager's Manual vm-install-jobs(8)NAME
vm-install-jobs - queries and manages VM creation jobs that were started by vm-install
SYNOPSIS
vm-install-jobs [options ...]
DESCRIPTION
VMs may be created by vm-install interactively, or as backgrounded jobs. The vm-install-jobs command manages backgrounded VM creation
jobs.
OPTIONS --cancel job-id
Cancels the specified job. If the VM is still running, it is stopped. This command may return before the VM is completely stopped
or the vm-install process has completely exited. The job is not implicitly deleted, so that the cancelation progress may be
observed.
--delete job-id
Deletes the specified job. The job must be in one of the FINISHED, FAILED, or CANCELED states. The VM's configuration is deleted,
as are any disks that were created during the job.
--detach job-id
Detaches the created VM from the specified job. The job must be in the FINISHED state. The job is deleted, but the VM's configura-
tion and its disks are left intact.
--list Lists all known VM creation jobs, by ID. One job ID is output per line.
--status job-id
Outputs the status of the specified job.
JOB STATES
Every job is always in one of the following states:
0: SETTINGS
1: PREP_INSTALL
2: INSTALL
3: POST_INSTALL
4: RUNTIME_CONF
5: RUNTIME
6: FINISHED
7: FAILED
8: CANCELED
The normal progression is from state 0 to state 6. States 6, 7, and 8 are terminal states.
JOB STATUS
Querying the job status will print (to stdout) a number of key/value pairs. The possible keys and their meanings are:
exit The exit code of the VM creation job. This key is only present once the job is in one of the states FINISHED, FAILED, or CANCELED.
To interpret the meaning of the exit code, see vm-install(8)
id The job ID. Always present.
inotify
A filename to monitor (via inotify(7) ) for state changes. The recommended inotify mask to use is IN_CLOSE_WRITE. Always present.
log The location of the log file. Always present.
pid The process ID of the VM creation job. This key is only present if the VM creation process is still running. The PID is used
internally to cancel the job.
state The job's current state. See JOB STATES. Always present.
uuid The VM's UUID. This key is only present once all of the VM's settings have been gathered.
vnc The last known location to view the VM's console via VNC. Note that the presence of this key does not guarantee that the VM is cur-
rently running. When no authentication is necessary, the URL will be ip::port. If authentication is necessary, the URL will be
username:password@ip::port.
DIAGNOSTICS
A zero exit code indicates success; non-zero indicates failure.
Note that the exit code of this tool indicates the success of the job management command. It does not represent the success or failure of
the job itself.
SEE ALSO
To interpret the exit code of a job or of this command, see vm-install(8)
To monitor state changes of jobs, see inotify(7)
To report problems with this software or its documentation, visit http://bugzilla.novell.com
2007-02-01 vm-install-jobs(8)