tl;dr The cause of the problem is that gulp (and any other command that shows this message) is actually a batch file (*.cmd, *.bat) and the behavior is built into cmd.exe, the interpreter of batch files. Package managers are increasingly providing PowerShell scripts (*.ps1) as well (see bottom section), which bypasses the problem when running … Read more
What he meant is that job control is by default turned off in non-interactive mode (i.e. in a script.) From the bash man page: JOB CONTROL Job control refers to the ability to selectively stop (suspend) the execution of processes and continue (resume) their execution at a later point. A user typically employs this facility … Read more
To ‘background’ a process when you start it Simply add an ampersand (&) after the command. If the program writes to standard out, it will still write to your console / terminal. To foreground the process Simply use the fg command. You can see a list of jobs in the background with jobs. For example: … Read more
There’s a bash builtin command for that. wait [n …] Wait for each specified process and return its termination sta‐ tus. Each n may be a process ID or a job specification; if a job spec is given, all processes in that job’s pipeline are waited for. If n is not given, all currently active … Read more
SIGTERM tells an application to terminate. The other signals tell the application other things which are unrelated to shutdown but may sometimes have the same result. Don’t use those. If you want an application to shut down, tell it to. Don’t give it misleading signals. Some people believe the smart standard way of terminating a … Read more
Yes, absolutely: screen(1) is the answer. To get started, add screen -R to ~/.bash_profile or equivalent, log out, and log back in. To continue what’s running in the background, press Control-A then N. This will create a new terminal screen in the foreground while seamlessly continuing your running process on the background. Press Control-A then … Read more
You can kill by job number. When you put a task in the background you’ll see something like: $ ./script & [1] 35341 That [1] is the job number and can be referenced like: $ kill %1 $ kill %% # Most recent background job To see a list of job numbers use the jobs … Read more
Oh, god! No no no. Don’t use kill -9. It doesn’t give the process a chance to cleanly: shut down socket connections clean up temp files inform its children that it is going away reset its terminal characteristics and so on and so on and so on. Generally, send 15, and wait a second or … Read more
for DIR in * ; do rsync -a $DIR example.com:somewhere/ || break; done This will also exit the loop if an individual rsync run fails for some reason.