From: Jonathan Williams (jonathw@shubertorg.com)
Date: Wed Jun 12 2002 - 14:31:56 EDT
Ok, I go a few replies so figure I should make a proper summary. Here they are:
Dr. Thomas Blinn wrote:
>There is no way to associate a disconnected job like that with a new
>stdin/stdout/stderr (that is, a new controlling terminal). It would
>be nice to be able to do this, but there's no facility in the product
>code.
>
>If the job tries to access the X display, it will get an error, but
>depending on what it does with the error (that is, the exact logic in
>the program), that may or may not cause a problem.
>
>I tend to run long-running processes in a batch or at job (I usually
>use "at" over "batch"). The system (cron) creates a log file in /tmp
>with all the job output messages (both stdout and stderr are logged
>in the file), and mails it to you on job completion if there are no
>errors. While the job is running, you can read the file (e.g., you
>can do a "tail -f" on it in a window), since you own the file if you
>submitted the job. If the job is running on a remote server, then by
>using "at" or "batch" you know that as long as the server stays up and
>running, the job will run to completion, even if the remote system from
>which you submitted it dies or you lose the network connection or...
>
>Tom
Tim Cutts wrote:
>The short answer is no, but you can use a program like 'screen' to start
>processes in a terminal which is detachable. This program is a godsend
>for sysadmins - you can start something going at work, detach the
>terminal, go home, dial in and reattach to see how far it's got. Cool!
>
>You can download the sources from www.debian.org, amongst other places.
>The Linux sources compile fine on Tru64.
Jonathan Williams
Unix Systems Administrator
The Shubert Organization, Inc.
----- Original Message -----
From: "Jonathan Williams" <jonathw@shubertorg.com>
To: "Tru64 (E-mail)" <tru64-unix-managers@ornl.gov>
Sent: Tuesday, June 11, 2002 7:47 PM
Subject: Job in Limbo
> Hi, I had a job running on my desktop from one of our ES40's (5.1 patch 3)
> through an excursion DECterm connection. I lost power to my office, so
> obviously the DECterm session closed as well. I just checked and the job is
> running still (thank goodness), but its just got ?? where the terminal would
be.
> Is there anyway to reconnect this job to a terminal so I can watch its
progress?
> Or do I just have to let it finish. This particular job will finish without
any
> user intervention, so it would never stop to wait at a prompt or anything.
> Also, losing the displlay of the job wouldn't effect the job would it? Should
I
> just cancel this job and start over? I'm running an Informix dbimport (which
> has been running for 22 hours so far). Any help would be appreciated.
>
> Jonathan Williams
> Unix Systems Administrator
> The Shubert Organization, Inc
>
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:43 EDT