Let's assume I have a file named confirmation.sh with the following content:
#!/bin/bash
echo -n "Are you sure [Y/n]? "
read line
case "$line" in
n|N) echo "smth"
;;
y|Y) echo "smth"
;;
esac
and I want to run this script in the following way:
cat confirmation.sh | sh
I see Are you sure [Y/n]? and the script is interrupted. What's the problem?
As others have said, this is because the stdin of sh has been redirected to read from the pipe, it is not connected to the terminal as it would normally be. One thing you can do to get around this is to use /dev/tty to force the script to read from the terminal. Eg:
#!/bin/sh
read -p "Are you sure [Y/n]?" line </dev/tty
case "$line" in
y|Y) echo "confirmed"
;;
*) echo "not confirmed"
;;
esac
Normally you would only do this if you specifically want to prevent people from scripting the input, eg:
echo Y | sh confirmation.sh
This would still read from the terminal even though the user might expect this to automatically input Y at the prompt. It is common for programs that expect a password to do this.
sh 3<<CONFIRM /dev/fd/3
$(cat ./confirmation.sh)
CONFIRM
sh 3<./confirmation.sh /dev/fd/3
note: thanks to @Graeme for correcting me on the above two examples...
Its a lot easier to do if you keep stdin clear.
2<./confirmation.sh . /dev/stderr
Or, since a terminal's 0 1 2 are all the same file, just add:
read line <&2
And your
cat ./confirmation.sh | sh
Works just fine.
stderr though. I probably should though, I don't understand why.
This has worked for a single argument being piped to my script:
if [ -p /dev/stdin ]; then set -- "$( cat )"; fi
I can then access the piped data in a positional argument ($1), which is compatible with my other script workings.
From info test:
[ -p /dev/stdin ]:-p FILEis True if FILE exists and is a named pipe.
The short answer is you can't. The pipe redirects stdout to stdin, so therefore you cannot run an interactive script, as you have already redirected the output from the first command as the input to the second command in the pipe statement.
You might be looking to do something like this:
cat confirmation.sh > ask.sh && sh ask.sh
sh confirmation.sh?
/bin/bashin the bang line, yet you use a.shextension and try to pipe the script tosh. Not a problem since the code you have is compatible with both, but worth pointing out.