10-12-2005
Yeah, that is what I figured.
That being said, there must be some way to send a job to another session that you can manage remotely. Using screen, or somehow exporting the session in some way must allow for this capability. I can't imagine that unix, with all its power, there would be no way for a sysadmin to start a job at a terminal, then log in from home later on to check the status. I guess you could setup some cron job, but that is not what I want.
Another example:
I want to ssh from home to my work machine, then start a long job (recompile kernel, for example), then exit my session.
I then want to ssh back in at a later time, and see if the job has finished.
There must be someway to do this!
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
i have a problem with turning a job into backgrund.
When i enter this at the shell:
spice -b darlington.cir -r output.raw > screenout.tmp &
and then let me show the currently running jobs, i get the following output:
+ Suspended (tty output) spice -b darlington.cir -r output.raw >... (4 Replies)
Discussion started by: qsi
4 Replies
2. Programming
Hi there,
I'm quite new to UNIX for programming. I have a script that does this:
Shows on screen real-time results taken from phone calls and logs them in a file.
However, when I start my script, I want my script to start logging in the file in the background, so I can continue working on... (1 Reply)
Discussion started by: Jeremiorama
1 Replies
3. Shell Programming and Scripting
i need to execute 5 jobs at a time in background and need to get the exit status of all the jobs i wrote small script below , i'm not sure this is right way to do it.any ideas please help.
$cat run_job.ksh
#!/usr/bin/ksh
####################################
typeset -u SCHEMA_NAME=$1
... (1 Reply)
Discussion started by: GrepMe
1 Replies
4. UNIX for Advanced & Expert Users
Reposting, as it got lost during the database backup. :(
Via a shell script a spawn 3 background jobs namely a, b & c.
These will take different times to complete.
I want to print a different message on completion of each.
How can i find out when each one has completed independently.
... (19 Replies)
Discussion started by: vibhor_agarwali
19 Replies
5. UNIX for Dummies Questions & Answers
If I run a job in the background and logoff. Will the job continue to run or will my processes be killed ? (1 Reply)
Discussion started by: jxh461
1 Replies
6. Shell Programming and Scripting
We had a generic process where the jobs are scheduled to run sequentially and in background. We are noticing the problems with the background jobs.
Error Message:
/bin/ksh: /home/suren/bin/GenericReportScript.sh: cannot execute
The same script is existing in bin and it had enough... (2 Replies)
Discussion started by: sureng
2 Replies
7. Shell Programming and Scripting
Hi All,
Can someone help me in knowing the exact difference between nohup and &.
The definition is quite clear but i only want to know if i run my job using & and in between i hung up my terminal. (10 Replies)
Discussion started by: Uinx_addic
10 Replies
8. Shell Programming and Scripting
Hi,
I have a problem runnig from script two diferents process in background mod. Is there a limitation to do this?
For example
echo "Running process one:"
./ProcessOne &
echo "Running process two:"
./ProcessTwo &
echo "The process are runnig. Bye"
The problem is that the... (7 Replies)
Discussion started by: Xedrox
7 Replies
9. Red Hat
I have used shc utillity to convert a shell script to it's compiled version.Inside this script i have called another shell script which is also in compled version.
Example:-
Main script:- main.sh.x
child script:- child.sh.x (this is called inside main.sh.x)
This child script will run in... (2 Replies)
Discussion started by: millan
2 Replies
10. AIX
Hello,
Please advise use of screen in running jobs in nohup background and how to use this
Best regards,
Vishal (1 Reply)
Discussion started by: Vishal_dba
1 Replies
jobs(1) General Commands Manual jobs(1)
NAME
jobs - Displays status of jobs in the current session
SYNOPSIS
jobs [-l | -p] job_id...
[Tru64 UNIX] jobs [-n] job_id...
Note
The C shell has a built-in version of the jobs 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/jobs. 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:
jobs: XCU5.0
Refer to the standards(5) reference page for more information about industry standards and associated tags.
OPTIONS
Provides more information about each job listed. This information includes the job number, current job, process group ID, state and the
command that formed the job. Displays only the process IDs for the process group leaders of the selected jobs. [Tru64 UNIX] Displays
jobs that have stopped or exited since last notified.
By default, the jobs utility displays the status of all stopped jobs, running background jobs and all jobs whose status has changed and has
not been reported by the shell.
OPERANDS
Specifies the jobs for which the status is to be displayed. If no job_id operand is given, the status information for all jobs is dis-
played. The format of job_id is described in the Jobs section of the ksh(1) reference page.
DESCRIPTION
The jobs utility displays the status of jobs that were started in the current shell environment.
When jobs reports the termination status of a job, the shell removes its process ID from the list of those "known in the current shell exe-
cution environment". See the Jobs section of the ksh(1) reference page.
RESTRICTIONS
The jobs 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 jobs: 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 and informative messages written to standard output.
Determines the location of message catalogues for the processing of LC_MESSAGES.
SEE ALSO
Commands: bg(1), csh(1), fg(1), kill(1), ksh(1), sh(1p), wait(1)
Standards: standards(5)
jobs(1)