When nohup works, it's great. But when it doesn't ( e.g. asks for a
password or confirmation a few minutes after starting ), it can be a bummer.
For those not familiar with screen, here are five basic commands to get
started:
# to create a screen session
screen
# to detach from a screen session
^Ad ( that is, Ctrl + A, then d )
# to list running screen sessions ( list is of the form {pid}.{other stuff}
)
screen -ls
# to attach to a running screen session
screen -x {pid of running screen session}
# to stop a running screen session
exit # do this from within a screen session
There are a lot more options and lots of other really cool things that can
be done with screen and even more with tmux. But those five will get you
started.
BTW, another option for running long commands in the background is to use
Docker. :)
Enjoy,
- Robert
On Tue, Sep 17, 2019 at 2:19 PM <tomas.kuchta.li...@gmail.com> wrote:
> This would be the time to bring up - screen or tmux sessions as an
> alternatives
> to nohup.
>
> If you logout/disconnect from screen/tmux sessions - you can reconnect
> later to
> see the progress or how it all finished.
>
> Tomas
>
> On Tue, 2019-09-17 at 14:05 -0700, Galen Seitz wrote:
> > On 9/17/19 2:00 PM, Rich Shepard wrote:
> > > On Tue, 17 Sep 2019, Rich Shepard wrote:
> > >
> > > > each takes 30+ minutes on my 1.8GB FiOS line. The list is in a bash
> > > > script
> > >
> > > Oops! That's 1.8MB/sec.
> >
> > Unless you're planning to logout after executing the script, nohup
> > should not be needed.
> >
> > galen
> _______________________________________________
> PLUG mailing list
> PLUG@pdxlinux.org
> http://lists.pdxlinux.org/mailman/listinfo/plug
>
_______________________________________________
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug
