>running script for multiple days, saves output at end of script
>lose ssh connection for .001 seconds
>reconnect
>script is not running
so this is the power of GNU/Linux
Running script for multiple days, saves output at end of script
Adam Baker
Other urls found in this thread:
pubs.opengroup.org
twitter.com
Jose Foster
make it save output while it's running
Alexander Adams
screen autodetach solves this
I never run an ssh session without screen, not only for this but also because multiplexing is just too useful
Levi Morris
screen -h1000 -R whatever
[run your script here]
press ctrl+a then press d
log out of ssh or whatever
reconnect with
screen -r whatever
OR
nohup ./script &
lrn 2 background
Jordan Scott
Use tmux or run it as a daemon.
Bentley Morris
It's not "GNU/Linux" problem. It is "you" problem.
Christian Ortiz
Microsoft(tm) RDP does not have this problem.
Jaxson Green
wow I remember when I was that young
Wyatt Nelson
Kek, didnt use screen or tmux
Isaac Martin
this
instead of ricing your desktop with anime girls learn some commands
also checked
Ryan Bailey
>winjeet doesn't know how to use Unix, the thread
Aaron Flores
lmao nigger
Evan Williams
>retard doesnt use thing right
>blame thing for not popping up a Clippy tooltip when he does something wrong
man nohup
Christian Garcia
You should have used screen. Also saving intermediate steps to files is standard practice if you have multiple days runs.
William Cox
you could've just googled "how to run a script in background on linux", but instead you decided to pollute the board with this garbage thread
have some shame of yourself, faggot
Grayson Walker
There's a tool just for this, OP:
pubs.opengroup.org
Ryder Butler
no one cares about FAGMAN software
Jacob Brown
A long running script should always be daemonized, either by being backgrounded or running in a detached shell instance.
Joshua Edwards
use tmux
Ayden Foster
why do I come to this fucking site
Dominic Campbell
Apparently to get called a retard because you don't know how to use Google lol