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
proto(4) Kernel Interfaces Manual proto(4)
NAME
proto - prototype job file for at
SYNOPSIS
DESCRIPTION
When a job is submitted to or the job is constructed as a POSIX shell script (see at(1)). The job file is created in as follows:
o creates a header describing the job as an job or a job. jobs submitted to all queues other than queue are listed as jobs. The header
is:
for an job, or
for a job.
o A set of POSIX shell commands is added to make the environment (see environ(5)) for the job the same as the current environment.
o then copies text from the prototype file to the job file, except for special variables that are replaced by other text:
Replaced by the current working directory.
Replaced by the current file size limit (see
ulimit(2)).
Replaced by the current umask (see
umask(2)).
Replaced by the time at which the job should be run,
expressed as seconds since January 1, 1970, 00:00 Coordinated Universal Time, preceded by a colon.
Replaced by text read by
from the standard input (that is, the commands provided to to be run in the job).
o When a job is submitted to queue queue, uses the file as the prototype file if it exists. Otherwise, it uses the file
EXAMPLES
The following file creates commands to change the current directory, file size limit, and umask in the job to their respective values as
they existed when was originally run. These commands are inserted before the commands in the job:
SEE ALSO
at(1), queuedefs(4).
STANDARDS CONFORMANCE
proto(4)