Just a quick note - there is practically no learning curve to screen. You can start it with just 'screen' then run whatever commands you want, and then you can disconnect it with Ctrl-a d. (Ctrl-a pushed together, then release both, then press d by itself.) Then 'screen -r' will reconnect to it to check what it's doing.
Of course there are tons more options, but these are really what I mainly use it for. I love being able to disconnect from the machine while leaving my processes running. I even run screen from cron sometimes, if it's a recurring job that I want to be able to check in on while it's running. (For example, one that might run for days... :) ) On Thu, Mar 2, 2017 at 10:55 AM, Rich Shepard <rshep...@appl-ecosys.com> wrote: > On Thu, 2 Mar 2017, Tom wrote: > > > To see if your background process does something with the CPU rather than > > just hang around waiting for user input for example - you could see the > > process CPU load and wall clock time - the time should be increasing. The > > easiest way is to fire: top and see what CPU percentage the process uses > > and if the TIME+ metrics is increasing. > > > Tom, > > The model runs without user input. I ran top and it showed python > running > (because the model's written in python). I don't recall what the time > metrics showed. > > > Please note that some processes do not run in background - if you put > > them in background they sleep until they are in foreground. If that is > > the case for your process, you need screen, tmux or vnc to keep the > > process in the foreground. Also some progress indicator - in a log file > > perhaps would be great to have for long running applications. > > It could be that this model does not like running in the background. > I've > modified a couple of run parameters and started it again, but in the > foreground this time. The author tells me that the completion ETA will > increase until soils are saturated, then decrease drastically. I'm looking > forward to seeing a decrease in ETA because now the model run is 1.3% > completed and the ETA is 3 days, 12 hours, and increasing. :-) > > I've not before run a hydrologic model over a 25 day period with > precipitation specified in mm/hr. A learning experience all around. > > Thanks, > > Rich > _______________________________________________ > PLUG mailing list > PLUG@lists.pdxlinux.org > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list PLUG@lists.pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
