Shell – How to Remove ^C When Pressing CTRL+C

By default, shells expand wildcards if a file matches them but keep unexpanded without match. For example, if you run touch /tmp/111; touch /tmp/11* this will create and then update mtime on /tmp/111, but if /tmp is empty but you call touch /tmp/11* you will get file named "11*" in /tmp.

This is rather weird feature of shells. Sometimes proper expanding isn't possible without special hacks as intermediate function. Most current shells invent special options for typical cases; e.g. "shopt -s failglob" in bash rejects it from running any command where wildcard match fails.

One shall rely on find's wildcard expanding, so such pattern shall be quoted against expansion in shell:

find /home/primbat/testing -name 'sftp_bcs_report_*.log' -type f -ctime +7

(note single quotes). With zero or one file, it works, but with two or more files you get broken command syntax and it complains - this is what is said by colleague Arcege. Your "set -f" disables expansion totally - well, it is good measure for diagnostics but can give underwater rakes for a future moving. Quotes are simpler:)

If you type

command 1 & command 2

this is equal to

command 1 &
command 2

i.e. this will run the first command in background and then runs the second command in foreground. Especially this means, that your echo "done" is printed after command 2 finished even if command 1 is still running.

You probably want

command 1 &
command 2 &
wait
echo "done"

This will run both commands in background and wait for both to complete.

If you press CTRL-C this will only send the SIGINT signal to the foreground process, i.e. command 2 in your version or wait in my version.

I would suggest setting a trap like this:

#!/bin/bash

trap killgroup SIGINT

killgroup(){
  echo killing...
  kill 0
}

loop(){
  echo $1
  sleep $1
  loop $1
}

loop 1 &
loop 2 &
wait

With the trap the SIGINT signal produced by CTRL-C is trapped and replaced by the killgroup function, which kills all those processes.