Sponsored Content
Top Forums Shell Programming and Scripting HERE Document in Shell Script Post 302972631 by nishant.kansal@ on Monday 9th of May 2016 05:31:49 AM
Old 05-09-2016
HERE Document in Shell Script

Hi,

I have a shell script to install one of our products. It comprises of commands that are specific to the product installation. These commands require user inputs at different stages.

To avoid manual feeding of inputs every time, I tried using HERE document.

it is like-
Code:
#! /usr/bin

command1 -console <<EOF
1
2
3
EOF

command2 -console <<EOF
1
2
0
3
EOF

....

HERE is working perfectly fine for all the commands except one. In that, moment it reaches to a particular option, instead of taking the input from HERE, it simply skips rest of the options and proceeds further without any error.

I tried capturing the output and errors, however, since, it is not resulting in any error at that stage, it is not capturing anything.

Can anyone please help me in how to troubleshoot it? Or, any other workaround?

Thanks,
Nishant



Moderator's Comments:
Mod Comment Please use code tags as required by forum rules!

Last edited by RudiC; 05-09-2016 at 06:35 AM.. Reason: Added code tags.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

here document to automate perl script that call script

I am trying to use a here document to automate testing a perl script however when the perl script hits a system(perl subscript.pl) call, input is no longer entered into this subscript. here is my script $ cat test.sh #ksh for testcase do program <<-EOF | tee -a funcscnlog.log y... (3 Replies)
Discussion started by: hogger84
3 Replies

2. Programming

UNIX Shell Script to Create a Document of a PLSQL code.

Hi All, I am supposed to present the documentation for the PLSQL code (PACKAGES, PROCEDURE, FUNCTIONS) of my application. There are sufficient comments in my code. Has anyone written any Shell Script Utility which can parse the PLSQL code and generate some kind of document ( preferrably HTML not... (1 Reply)
Discussion started by: gauravsachan
1 Replies

3. Shell Programming and Scripting

Shell Scripted Document Management System

Over the past 4 -5 years, I have cobbled together a rudimentary 'Document Management System' for a school district I support using Linux Bash Shell scripts.. The purpose of the scripting was to supplement features of a Job Applicant Center that had very simplistic methods of handle file... (1 Reply)
Discussion started by: rmuledeer
1 Replies

4. Shell Programming and Scripting

Here document and shell scripting

Hi I am unable to spot a error with my here document in the shell script. for sid in $sids do ORACLE_SID=sid ORACLE_HOME=$(grep $sid $ORATAB_LOC |cut -f2 -d':') $ORACLE_HOME/bin/sqlplus -s /nolog <<EOF @$HOME/sql/checkdb-status.sql EOF done I am getting the error... (8 Replies)
Discussion started by: xiamin
8 Replies

5. Shell Programming and Scripting

Modifying XML document with Unix Script

Hi, I have xml documents that I want to change a value in, I can do it using sed in a text document but not the xml document. I have read other posts that allow the change between tags but the part I wish to change is only a small part of data with the tags. e.g. <?xml version="1.0"... (2 Replies)
Discussion started by: heather.morton@
2 Replies

6. UNIX for Dummies Questions & Answers

Need Shell Script for document searching

I need a script that reads only printable characters (no duplicates) from all files in a directory and output them in a text file. (2 Replies)
Discussion started by: l20N1N
2 Replies

7. Shell Programming and Scripting

Oracle Shell script | here document `EOF' unclosed

Hi folks I m creating script which is give me below error. $ ./function.ksh ./function.ksh: here document `EOF' unclosed Inside the script is #!/bin/ksh export ORACLE_SID=OECDV1 export ORACLE_HOME=/u01/app/oracle/product/10.2.0 export PATH=$ORACLE_HOME/bin:$PATH echo "sql is... (3 Replies)
Discussion started by: tapia
3 Replies

8. Shell Programming and Scripting

Perl script for taking inputs from one script and storing them into a document.

Hi. I wanted to create a Perl script which can take the outputs of a Perl script as it's input and temporarily store them in a document. Need help. Thanks.:) (8 Replies)
Discussion started by: xtatic
8 Replies

9. Shell Programming and Scripting

Is it possible to create a here document by running a script interactively?

hi, i have script which installs around 20 packages. during installation of each package script will be prompted for user input. i need to run the script in non-interactive by using here document. is it possible to generate here document by running the script in interactive mode on Solaris?... (1 Reply)
Discussion started by: snreddy_gopu
1 Replies

10. UNIX for Beginners Questions & Answers

UNIX Shell Script to Remove MongoDB Document-Based on Many inputs

Here I am in a position to write a Unix Shell script(.sh) to remove MongoDB collection documents. I know how to remove based on a condition like below and it works for me. eval 'db.Collection.remove({TimeStamp:{$lte: "'$var'"}}) But I need to change the remove statement based on a new parameter... (1 Reply)
Discussion started by: senthilmadhanT
1 Replies
GIMPTOOL-2.0(1) 					      General Commands Manual						   GIMPTOOL-2.0(1)

NAME
gimptool-2.0 - script to perform various GIMPy functions SYNOPSIS
gimptool-2.0 [--prefix[=DIR]] [--exec-prefix[=DIR]] [--version] [--help] [--quiet] [--silent] [-n] [--just-print] [--dry-run] [--recon] [--msvc-syntax] [--bindir] [--sbindir] [--libexecdir] [--datadir] [--sysconfdir] [--sharedstatedir] [--localstatedir] [--libdir] [--infodir] [--mandir] [--includedir] [--gimpplugindir] [--gimpdatadir] [--libs] [--libs-noui] [--cflags] [--cflags-noi] [--build plug-in.c] [--build-strip plug-in.c] [--install plug-in.c] [--install-strip plug-in.c] [--install-admin plug-in.c] [--install-bin plug-in] [--install-admin-strip plug-in.c] [--install-bin-strip plug-in] [--install-admin-bin plug-in] [--install-script script.scm] [--install-admin-script script.scm] [--uninstall-bin plug-in] [--uninstall-admin-bin plug-in] [--uninstall-script script.scm] [--unin- stall-admin-script script.scm] DESCRIPTION
gimptool-2.0 is a tool that can, among other things, build plug-ins or scripts and install them if they are distributed in one source file. gimptool-2.0 can also be used by programs that need to know what libraries and include-paths GIMP was compiled with. gimptool-2.0 uses pkg- config for this task. For use in Makefiles, it is recommended that you use pkg-config directly instead of calling gimptool-2.0. OPTIONS
gimptool-2.0 accepts the following options: --version Print the currently installed version of GIMP on the standard output. --help Print out the help blurb, showing commonly used commandline options. --quiet Run quietly without echoing any of the build commands. --silent Run silently without echoing any of the build commands. Same as --quiet. -n Test mode. Print the commands but don't actually execute them. Useful for making dry runs for testing. --just-print Test mode. Print the commands but don't actually execute them. Same as -n. --dry-run Test mode. Print the commands but don't actually execute them. Same as -n. --recon Test mode. Print the commands but don't actually execute them. Same as -n. --msvc-syntax Useful on Windows. Outputs the compiler and linker flags in the syntax used by Microsoft's toolchain. Passed to the pkg-config com- mand that does most of gimptool-2.0's work. --bindir Outputs the bindir used to install the GIMP. --sbindir Outputs the sbindir used to install the GIMP. --libexecdir Outputs the libexecdir used to install the GIMP. --datadir Outputs the datadir used to install the GIMP. --sysconfdir Outputs the sysconfdir used to install the GIMP. --sharedstatedir Outputs the sharedstatedir used to install the GIMP. --localstatedir Outputs the localstatedir used to install the GIMP. --libdir Outputs the libdir used to install the GIMP. --infodir Outputs the infodir used to install the GIMP. --mandir Outputs the mandir used to install the GIMP. --includedir Outputs the includedir used to install the GIMP. --gimpdatadir Outputs the actual directory where the GIMP data files were installed. --gimpplugindir Outputs the actual directory where the GIMP plug-ins were installed. --build plug-in.c Compile and link plug-in.c into a GIMP plug-in. --build-strip plug-in.c Compile,link, and strip plug-in.c into a GIMP plug-in. --install plug-in.c Compile, link, and install plug-in.c into the user's personal GIMP plug-in directory ($HOME/.gimp-2.6/plug-ins) --install-strip plug-in.c Compile, link,strip, and install plug-in.c into the user's personal GIMP plug-in directory ($HOME/.gimp-2.6/plug-ins) --install-admin plug-in.c Compile, link, and install plug-in.c into the system-wide GIMP plug-in directory (/usr/lib64/gimp/2.0/plug-ins) --install-bin plug-in Install plug-in into the user's personal GIMP plug-in directory ($HOME/.gimp-2.6/plug-ins) --install-admin-bin plug-in Install plug-in into the system-wide GIMP plug-in directory (/usr/lib64/gimp/2.0/plug-ins) --install-bin-strip plug-in Install stripped plug-in into the user's personal GIMP plug-in directory ($HOME/.gimp-2.6/plug-ins) --install-admin-bin-strip plug-in Install stripped plug-in into the system-wide GIMP plug-in directory (/usr/lib64/gimp/2.0/plug-ins) --install-script script.scm Install script.scm into the user's personal GIMP script directory ($HOME/.gimp-2.6/scripts) --install-admin-script script.scm Install script.scm into the system-wide GIMP script directory (/usr/share/gimp/2.0/scripts) --uninstall-bin plug-in Uninstall plug-in from the user's personal GIMP plug-in directory ($HOME/.gimp-2.6/plug-ins) --uninstall-admin-bin plug-in Uninstall plug-in from the system-wide GIMP plug-in directory (/usr/lib64/gimp/2.0/plug-ins) --uninstall-script script.scm Uninstall script.scm from the user's personal GIMP script directory ($HOME/.gimp-2.6/scripts) --uninstall-admin-script script.scm Uninstall script.scm from the system-wide GIMP script directory (/usr/share/gimp/2.0/scripts) --libs Print the linker flags that are necessary to link a GIMP plug-in. --libs-noui Print the linker flags that are necessary to link a GIMP plug-in, for plug-ins that do not require the GTK+ libraries. --cflags Print the compiler flags that are necessary to compile a GIMP plug-in. --clags-noui Print the compiler flags that are necessary to compile a GIMP plug-in for plug-ins that do not require the GTK+ libraries. --prefix=PREFIX If specified, use PREFIX instead of the installation prefix that GIMP was built with when computing the output for the --cflags and --libs options. This option is also used for the exec prefix if --exec-prefix was not specified. This option must be specified before any --libs or --cflags options. --exec-prefix=PREFIX If specified, use PREFIX instead of the installation exec prefix that GIMP was built with when computing the output for the --cflags and --libs options. This option must be specified before any --libs or --cflags options. ENVIRONMENT
CC to get the name of the desired C compiler. CFLAGS to get the preferred flags to pass to the C compiler for plug-in building. DESTDIR to add a prefix to the install/uninstall path. LDFLAGS to get the preferred flags for passing to the linker. LIBS for passing extra libs that may be needed in the build process. For example, LIBS=-lintl . PKG_CONFIG to get the location of the pkg-config program that is used to determine details about your glib, pango, gtk+ and gimp installation. SEE ALSO
gimp(1), gimprc(5), pkg-config(1) AUTHORS
gimptool was written by Manish Singh (yosh@gimp.org) and is based on gtk-config by Owen Taylor (owen@gtk.org). This man page was written by Ben Gertzfield (che@debian.org), and tweaked by Manish Singh (yosh@gimp.org), Adrian Likins (adrian@gimp.org) and Marc Lehmann (pcg@goof.com>). GIMP Manual Pages Version 2.6.8 GIMPTOOL-2.0(1)
All times are GMT -4. The time now is 06:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy