20 мар. 2010 г. · In Bash & ksh, you can make all stdout disappear by appending 1>/dev/null to the command. For csh and tcsh it's $1>/dev/null.

17 июл. 2009 г. · You can redirect the output of any program so that it won't be seen. $ program > /dev/null This will redirect the standard output - you'll still see any errors.

17 июл. 2009 г. · In bash, entering a "bg" puts the job into the background until it blocks needing input. It will continue to output to STDERR and STDOUT which might be ...

1 окт. 2011 г. · Yes, absolutely: screen(1) is the answer. To get started, add screen -R to ~/.bash_profile or equivalent, log out, and log back in.

20 июл. 2012 г. · If you're using BASH, just press CTRL - Z , which will suspend the process, and then use the bg command to send it to the background.

1 июл. 2009 г. · You can press ctrl-z to interrupt the process and then run bg to make it run in the background. You can show a numbered list all processes backgrounded in this ...

23 февр. 2010 г. · The other option is to use the screen command. The benefit of using screen is that you can reconnect to the process later. Share.

22 мая 2013 г. · You can run your process with nohup and write shell script to read nohup.out file which nohup uses to log . nohup command &. Share.

15 сент. 2011 г. · The best method is to start the process in a terminal multiplexer. Alternatively you can make the process not receive the HUP signal.

6 авг. 2013 г. · The log would tail in the background to your shell, and the prompt line would always stay perfectly at the bottom.