Igor Kromin |   Consultant. Coder. Blogger. Tinkerer. Gamer.

I've been having to write more than my usual share of shell scripts lately that orchestrate a number of other command line utilities and other shell scripts. Some of the scripts I've had to run from my script behaved well but some required user input and did not give any options to provide that input as command line arguments. Since I was not able to modify the scripts that I was calling, I had to find a different way to invoke them.
bash_read1.png


The scripts that I was calling used the 'read' command to prompt the user for input like so:
 External Script
read -p "Please enter input 1: " my_var1
read -p "Please enter input 2: " my_var2
read -p "Please enter input 3: " my_var3


These were interactive scripts but with a predictable pattern for input. Luck was on my side and I knew what each of these inputs should be while my script was being run. All I had to do was provide this input so that the external script would run as if it were a non-interactive script.

There are a number of ways to do the above, I went for something really simple, using echo and piping its output to the external script, like so:
 My Script
echo "MyInput1
MyInput2
MyInput3
" | external_script.sh


Note that the echo string is split across multiple lines, this is completely OK to do. Also note that after my 3rd input value there is a new line, that is because I needed that final return character since the 'read' command in the external script would be expecting that.

The same approach worked when the external script prompted for a password using 'read -s' too.

The above approach worked really well in my case, but it's not suitable for every occasion. In more complex situations the 'expect' command would do a better job, but I'll leave that for another article.



-i

Please leave your comments or feedback below!
comments powered by Disqus
Other posts you may like...
Hi! You can search my blog here ⤵
Or browse the recent top tags...

Recent Blog Posts

WebLogic Maven Plugin - How to fix the MojoExecutionException: The artifact location was not specified

jPhotoFrame version 0.4 released with a whole new layout engine

Upcycling a couple of old broken lamps to create something amazing

A custom exception mapper and writer for a RESTful JAX-RS Jersey service

How to fix Plex error - Sorry there was a problem playing this item

Jersey JAX-RS filters and interceptors execution order for a POST request

Fix your Mac - users not showing on the macOS login screen when FileVault is enabled

BMB-012 Nanoblock T-Rex Skeleton Model assembly

Writing a custom MessageBodyReader to process POST body data with Jersey

How to make Skype for Business responsive again on macOS

Recent Galleries

BMB-012 Nanoblock T-Rex Skeleton Model assembly

Tiny Arcade revision 6 kit assembly and decal application

Atari Lynx repair - Part 5 - McWill LED screen mod installation

Atari Lynx repair - Part 4 - screen cover replacement

Atari Lynx repair - Part 2 - re-capping the motherboard

Atari Lynx repair - Part 3 - broken speaker replacement

Atari Lynx repair - Part 1 - introduction and case disassembly

Building a custom Atari Lynx game box storage shelf unit in a day

Protecting old Atari Lynx game boxes with snug fit plastic sleeves

Monument Valley 2 is released and does not disappoint

Blogs and Friends

Matt Moores Blog
Georgi's FlatPress Guide
Perplexing Permutations
The Security Sleuth
Ilia Rogatchevski
Travelling Fairy

Blog Activity

Blog Activity