Sponsored Content
Full Discussion: execution of a script
Top Forums Shell Programming and Scripting execution of a script Post 302591003 by ragilla on Wednesday 18th of January 2012 08:09:06 AM
Old 01-18-2012
execution of a script

Hi

i have a small script like this
Code:
  $ cat test.sh
#!/usr/bin/sh
name="ram"
echo ${1}
set 1 2 3 4 5 6 7 8 9 0 123 o870
echo $9
echo ${12}

when i am trying to execute like below i am not getting the output

Code:
jena samp_perl $ sh test.sh
test.sh: This:  not found

but when i executing like below i am able to get the output
Code:
jena samp_perl $ ./test.sh 1
1
9
o870

so may i know wt is the difference between two types of executions and why i am not able to get the output when i tried like this sh test.sh...


please help me in this.. thanks in advance

Moderator's Comments:
Mod Comment Please use next time code tags for your code and data

Last edited by vbe; 01-18-2012 at 09:55 AM.. Reason: code tags
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

pb with script execution

Hello, Can somebody tell me the differnce between a call of a ksh with the dot : >. script.ksh and the call without the dot: >script.ksh In my script I have writen a test for the number of parameters: if then echo 'Usage : '$0 exit 1 fi as my script doesn't need any... (3 Replies)
Discussion started by: Cecile
3 Replies

2. Shell Programming and Scripting

help on script execution

Hi, Please help me on the below code of line of what it actually does ${Script_dir}/scrip1.sh & export script1_pid=$! ${Scipt_dir}/script2.sh & export script2_pid=$! ${Scrip_dIR}/script3.sh & export script3_pid=$! wait ${script1_pid} //could u tell me wht this... (8 Replies)
Discussion started by: sussane
8 Replies

3. Shell Programming and Scripting

Script to carry-over the script execution to another system

The situation is like this. If I need to know the parameters of all the unix servers connected to a common network, is it possible to get all the parameter details of all the system with the help of a script written in one server?? Can a script be written like that ? Let me give some... (3 Replies)
Discussion started by: yuvanash
3 Replies

4. Shell Programming and Scripting

Expect Issue Serial Forground Execution vs Concurrent Background Execution

I have an expect script that interrogates several hundred unix servers for both access and directories therein using "ssh user@host ls -l /path". The combination of host/path are unique but the host may be interrogated multiple times if there are multiple paths to test. The expect script is run... (2 Replies)
Discussion started by: twk
2 Replies

5. Shell Programming and Scripting

Script Execution

Hello all, I generally get 6 or more files at location /usr/example.Files listed below er 1 2 3 9.txt er 2 2 3 9.txt er 3 2 3 9.txt er 4 2 3 9.txt abc.next del pa.txt cr ad.txt ps tr as er.txt Now the issue is i need to transfer 2 files (one file is fixed called abc.next) at a... (12 Replies)
Discussion started by: j_panky
12 Replies

6. UNIX for Advanced & Expert Users

SSH using shell script terminates the script execution

Hello, I am writing a shell script in which i do ssh to remote server and count the number of files there and then exit. After the exit the shell script terminates which i believe is expected behavior. Can some one suggest me a way where even after the exit the script execution resumes. ... (2 Replies)
Discussion started by: manaankit
2 Replies

7. Emergency UNIX and Linux Support

invoke one script based on previous script execution

I am database guy and not very good at shell scripts. I am seeking help to sharp my script coding. I have 5 scripts 1. master script. I use this one to call other four scripts to do database work. 2. db_backup_1 and log_backup_1 3. db_backup_2 and log_backup_2 in master script, I want to... (4 Replies)
Discussion started by: duke0001
4 Replies

8. Solaris

Script on Solaris spawning 2 processes for one shell script execution

Hi, I am having a shell script on Solaris 10 which has a while loop as shown below. #!/usr/bin/ksh # while do sleep 60 done Name of the shell script is coldcentric.sh. I executed script /DATAWAREHOUSE/LOAD/Scripts/coldcentric.sh from a command task in Informatica worklow as... (3 Replies)
Discussion started by: chekusi
3 Replies

9. Shell Programming and Scripting

Freezes up execution of the script

My script that I wrote is no longer running, but just freezing when I execute it. Before it was running and showing me where errors were, now when I execute it, nothing happens and i cant type anything into the command screen. The script was a looping script, what could be going on? (8 Replies)
Discussion started by: MJCreations
8 Replies

10. UNIX for Advanced & Expert Users

Script execution

I need to call a script if the month end falls on Saturday or Sunday (5 Replies)
Discussion started by: bala1985
5 Replies
DH_INSTALLINIT(1)						     Debhelper							 DH_INSTALLINIT(1)

NAME
       dh_installinit - install service init files into package build directories

SYNOPSIS
       dh_installinit [debhelperoptions] [--name=name] [-n] [-R] [-r] [-d] [--params]

DESCRIPTION
       dh_installinit is a debhelper program that is responsible for installing init scripts with associated defaults files.  In compatibility
       levels up to 11, dh_installinit also handled upstart job files and systemd service files.

       It also automatically generates the postinst and postrm and prerm commands needed to set up the symlinks in /etc/rc*.d/ to start and stop
       the init scripts.

       In compat 10 or earlier: If a package only ships a systemd service file and no sysvinit script is provided, you may want to exclude the
       call to dh_installinit for that package (e.g. via -N).  Otherwise, you may get warnings from lintian about init.d scripts not being
       included in the package.

FILES
       debian/package.init
	   If this exists, it is installed into etc/init.d/package in the package build directory.

       debian/package.default
	   If this exists, it is installed into etc/default/package in the package build directory.

       debian/package.upstart
	   In compatibility level 11, this file will trigger an error with a reminder about ensuring the proper removal of the upstart file in the
	   previous package version.  Please consider using the "rm_conffile" feature from dh_installdeb(1) to ensure the proper removal of
	   previous upstart files.

	   In compatibility level 10, if this file exists, it is installed into etc/init/package.conf in the package build directory.

       debian/package.service
	   If this exists, it is installed into lib/systemd/system/package.service in the package build directory. Only used in compat levels 10
	   and below.

       debian/package.tmpfile
	   If this exists, it is installed into usr/lib/tmpfiles.d/package.conf in the package build directory. (The tmpfiles.d mechanism is
	   currently only used by systemd.) Only used in compat levels 10 and below.

OPTIONS
       -n, --no-scripts
	   Do not modify postinst/postrm/prerm scripts.

       -o, --only-scripts
	   Only modify postinst/postrm/prerm scripts, do not actually install any init script, default files, upstart job or systemd service file.
	   May be useful if the file is shipped and/or installed by upstream in a way that doesn't make it easy to let dh_installinit find it.

	   Caveat: This will bypass all the regular checks and unconditionally modify the scripts.  You will almost certainly want to use this
	   with -p to limit, which packages are affected by the call.  Example:

	    override_dh_installinit:
		   dh_installinit -pfoo --only-scripts
		   dh_installinit --remaining

       -R, --restart-after-upgrade
	   Do not stop the init script until after the package upgrade has been completed.  This is the default behaviour in compat 10.

	   In early compat levels, the default was to stop the script in the prerm, and starts it again in the postinst.

	   This can be useful for daemons that should not have a possibly long downtime during upgrade. But you should make sure that the daemon
	   will not get confused by the package being upgraded while it's running before using this option.

       --no-restart-after-upgrade
	   Undo a previous --restart-after-upgrade (or the default of compat 10).  If no other options are given, this will cause the service to
	   be stopped in the prerm script and started again in the postinst script.

       -r, --no-stop-on-upgrade, --no-restart-on-upgrade
	   Do not stop init script on upgrade.	This has the side-effect of not restarting the service as a part of the upgrade.

	   If you want to restart the service with minimal downtime, please use --restart-after-upgrade (default in compat 10 or later).  If you
	   want the service to be restarted but be stopped during the upgrade, then please use --no-restart-after-upgrade (note the "after-
	   upgrade").

	   Note that the --no-restart-on-upgrade alias is deprecated and will be removed in compat 12.	This is to avoid confusion with the
	   --no-restart-after-upgrade option.  The --no-stop-on-upgrade variant was introduced in debhelper 10.2 (included in Debian stretch).

       --no-start
	   Do not start the init script on install or upgrade, or stop it on removal.  Only call update-rc.d. Useful for rcS scripts.

       --no-enable
	   Disable the init script on purge, but do not enable them on install.  This implies a versioned dependency on init-system-helpers (=
	   1.51)> as it is the first (functional) version that supports <update-rc.d <script defaults-disabled>>.

	   Note that this option does not affect whether the services are started.  Please remember to also use --no-start if the service should
	   not be started.

	   Cannot be combined with -uparams, --update-rcd-params=params, or -- params.

       -d, --remove-d
	   Remove trailing d from the name of the package, and use the result for the filename the upstart job file is installed as in etc/init/ ,
	   and for the filename the init script is installed as in etc/init.d and the default file is installed as in etc/default/. This may be
	   useful for daemons with names ending in d. (Note: this takes precedence over the --init-script parameter described below.)

       -uparams --update-rcd-params=params
       -- params
	   Pass params to update-rc.d(8). If not specified, defaults (or defaults-disabled with --no-enable) will be passed to update-rc.d(8).

	   Cannot be combined with --no-enable.

       --name=name
	   Install the init script (and default file) as well as upstart job file using the filename name instead of the default filename, which
	   is the package name. When this parameter is used, dh_installinit looks for and installs files named debian/package.name.init,
	   debian/package.name.default and debian/package.name.upstart instead of the usual debian/package.init, debian/package.default and
	   debian/package.upstart.

       --init-script=scriptname
	   Use scriptname as the filename the init script is installed as in etc/init.d/ (and also use it as the filename for the defaults file,
	   if it is installed). If you use this parameter, dh_installinit will look to see if a file in the debian/ directory exists that looks
	   like package.scriptname and if so will install it as the init script in preference to the files it normally installs.

	   This parameter is deprecated, use the --name parameter instead. This parameter is incompatible with the use of upstart jobs.

       --error-handler=function
	   Call the named shell function if running the init script fails. The function should be provided in the prerm and postinst scripts,
	   before the #DEBHELPER# token.

NOTES
       Note that this command is not idempotent. dh_prep(1) should be called between invocations of this command. Otherwise, it may cause multiple
       instances of the same text to be added to maintainer scripts.

SEE ALSO
       debhelper(7)

       This program is a part of debhelper.

AUTHORS
       Joey Hess <joeyh@debian.org>

       Steve Langasek <steve.langasek@canonical.com>

       Michael Stapelberg <stapelberg@debian.org>

11.1.6ubuntu2							    2018-05-10							 DH_INSTALLINIT(1)
All times are GMT -4. The time now is 01:03 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy