If you started it with nohup; it will stay running until it exits on its own or is killed. The output of jobs (based on my reading) is local to the running shell. So each window/shell could result in different output. If the shell closes, the jobs list is removed. Current running jobs would receive a SIGHUP when the shell closes. NOHUP causes the shell to not send the signal, just like if disown job_num was issued.
These background jobs tend to be monitored by a status file. If you don't have some way to determine how far into the program/data the program has progressed you won't know it has stalled. Putting this in screen or tmux will allow you to come back to the session even if you have totally logged out of the machine. To check the status, login and re-attach to the (still) running session. On Thu, Mar 2, 2017 at 6:22 AM, Rich Shepard <[email protected]> wrote: > Knowing that a model would run for a long time I started it last Sunday > at > 8:10 am in the background by appending '&' to the command line. Since then > I > sporadically look at the status of that process ID and see the status as S, > which I understand is interruptible sleep. > > When I check status with 'jobs -l' there's nothing returned so why does > it > continue to display in the process list? > > Rich > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
