Hi,
Thanks in advance.
i need to kill a unix background running job after that job process completes.
i can kill a job by giving the following unix command
kill -9 processid
how to kill the job after the current process run gets completed ?
Appreciate your valuable help.
... (1 Reply)
Hi,
Thanks in advance.
i need to kill a unix background running job after that job process completes.
i can kill a job by giving the following unix command
kill -9 processid
how to kill the job after the current process run gets completed ?
Appreciate your valuable help.
Thanks... (7 Replies)
Hi everyone,
Please find the script for Filewatcher rule file,which does the simple job of moving the files whenever it dectects to another directory.And whenever it detects the cmd_mm.stop file,it should terminate the job.
INTERVAL 60
ON_FILEWATCH ${HLD}/CMD/* CREATE 0 1 2 0400 5
THEN... (2 Replies)
I have this box job and it contains only one job under it which is to load a file. I want to insert a "File Watcher", "Copy File" to it? Have no clue how to do that...any help plzzz... (4 Replies)
Hi All,
Sorry to post these many questions on UNIX. i am new to unix & got only UNIX work in my organization.
I need to make a script for File Arrival Check.
1. The script should wait for indicator file for configured amount of time.
2. If the file is not received after the configured... (4 Replies)
Hi Experts,
I need a script advice to schedule 12 jobs ( SAS Codes execute back ground ).
Algorithem:
1. Script checks first job.
2. Finds first job is done; invoke second job.
3. finds second job is done; invoke third job.
..
Request you to please assist. (3 Replies)
We need to configure autosys that when a job fails continously for 3 times, we need to call another job.
Is this possible in Autosys, or can anyone advice on the alternative. (2 Replies)
Hi,
A ------> B ------> C
I have a scenario where each day, my server B would ftp to server A and pull (A,B,C,D,E) from a specific directory.
Server C would need files (B,D) only when server B finished receiving from server A. These files change everyday, so sometimes it takes longer... (3 Replies)
Hi,
I have a requirement wherein i need to have a generic file watcher in place.
On presence of a file in a particular directory,the file watcher should identify the related config file and execute the series of the shell scripts mentioned in the config file.
eg.Config file
a.sh
b.sh... (7 Replies)
hi All,
I ned to write a filewatcher script, with following requirements.
1. The script should look for the file in every 5 min.
2. If the file is found, it should check in every 3 min the size of file.
3. if the file size has not changed in last 4 iterations (i.e. in last 12 min), the... (2 Replies)
Discussion started by: alok2082
2 Replies
LEARN ABOUT OSF1
fg
fg(1) General Commands Manual fg(1)NAME
fg - Runs jobs in the foreground
SYNOPSIS
fg [job_id...]
Note
The C shell has a built-in version of the fg command. If you are using the C shell, and want to guarantee that you are using the command
described here, you must specify the full path /usr/bin/fg. See the csh(1) reference page for a description of the built-in command.
STANDARDS
Interfaces documented on this reference page conform to industry standards as follows:
fg: XCU5.0
Refer to the standards(5) reference page for more information about industry standards and associated tags.
OPTIONS
None
OPERANDS
Specifies the job to be run as a foreground job. If no job_id operand is given, the job_id for the job that was most recently suspended,
placed in the background or run as a background job is used. The format of job_id is described in the Jobs section of the ksh(1) reference
page.
DESCRIPTION
If job control is enabled (see the description of set -m in the ksh(1) reference page), the fg utility moves a background job from the cur-
rent environment into the foreground.
Using fg to place a job into the foreground removes its process ID from the list of those "known in the current shell execution environ-
ment"; see the Jobs section of the ksh(1) reference page.
RESTRICTIONS
If job control is disabled, the fg utility exits with an error and no job is placed in the foreground. The fg utility does not work as
expected when it is operating in its own utility execution environment because that environment has no applicable jobs to manipulate.
EXIT STATUS
The following exit values are returned: Successful completion. An error occurred.
ENVIRONMENT VARIABLES
The following environment variables affect the execution of fg: Provides a default value for the internationalization variables that are
unset or null. If LANG is unset or null, the corresponding value from the default locale is used. If any of the internationalization vari-
ables contain an invalid setting, the utility behaves as if none of the variables had been defined. If set to a non-empty string value,
overrides the values of all the other internationalization variables. Determines the locale for the interpretation of sequences of bytes
of text data as characters (for example, single-byte as opposed to multibyte characters in arguments). Determines the locale used to
affect the format and contents of diagnostic messages written to standard error. Determines the location of message catalogues for the
processing of LC_MESSAGES.
SEE ALSO
Commands: bg(1), csh(1), jobs(1), kill(1), ksh(1), sh(1p), wait(1)
Standards: standards(5)fg(1)