05-17-2013
Naming your shellscripts with extension .sh (or .bash or .ksh,...) simply helps you to know that the file is actually a script without looking at its content.
Self documenting filenames make maintenance of a system easier.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
I have 2 scripts, one is the .profile and the other is a SID selector for Oracle Databases.
But when I call one from the other, even though it seems to have worked, it doesn't.
Can anyone help??
******************* .profile**********************
#!/bin/ksh
.... (5 Replies)
Discussion started by: dnkansah
5 Replies
2. Cybersecurity
they are having an operator call my home line and also my cell number and they are typing and the operator tells me what they are typing on their computer. i nevere heard of this. it is new to me. it is free the operator said, they knew my name and also a friend of mine's name...the phone says the... (2 Replies)
Discussion started by: gail
2 Replies
3. Shell Programming and Scripting
OK, I'm very new to shell scripting, and I'm trying to write a (very) simple wrapper for sendmail that outputs all the arguments as well as the file that called sendmail to an output file which can later be looked over.
Is it possible to get a file's name and path that called a script? (0 Replies)
Discussion started by: ghstber
0 Replies
4. UNIX for Dummies Questions & Answers
I have created a file generic.func and it has lots of functions. One of the functions is this:
Check_backup_size()
{
dsmc q b $BACKUP_DIR/"*.Z" | awk '{print $1}'|sed 's///g' > outputfile
X=`awk '{sum += $1} END {print sum }' outputfile'`
echo "$X"
ls -ltr $BACKUP_DIR/"*.Z" | awk... (5 Replies)
Discussion started by: ashika
5 Replies
5. Shell Programming and Scripting
Hi all,
The scenario is:
1. I created a script called hello
2. i created another script called blah which meant to use "hello" script.
How do i do it?
e.g. "blah" script
#!/bin/sh
test = /home/blah/hello
echo "please enter name"
read name
test $name
is it correct ? or i... (2 Replies)
Discussion started by: c00kie88
2 Replies
6. UNIX for Dummies Questions & Answers
I have created a shortcut for the file kill_process.sh as shown below.
alias kill_process="sh /root/kill_process.sh"
It is working as per my expectations. But I have 2 questions.
1) Is there any better way?
2) How do I check what does kill_process link to? (1 Reply)
Discussion started by: shantanuo
1 Replies
7. UNIX for Dummies Questions & Answers
Hi. I have a problem in running a program in linux system. This program (damaver.l86) is in the path /home/shenk/damaver/, and it needs to call another program (supcomb.l86) in another path /home/shenk/supcomb/. I tried to modified the .bash_profile, but it didn't work. The error message is always... (1 Reply)
Discussion started by: shenk
1 Replies
8. Programming
I have an adapter written in c++ from which I need to call a java service point.
Could anybody please provide an example program of calling java from c++
thanks in advance. (0 Replies)
Discussion started by: axes
0 Replies
9. Programming
Hello Again,
I am just wanted to know if we can call the Template using "require_once" at PHP?
Any views around happy to discuss.
Thanks in Advance (2 Replies)
Discussion started by: AimyThomas
2 Replies
10. Shell Programming and Scripting
Hi,
I need to run start_load function for two tables.
Step 1: if HMAX_TBL_ID and GMAX_TBLI_D are same for tab_name1 then echo message "all table ids are processed"
Step 2: go back and call start_load for tab_name2 and check if table id are same for table 2 too.
Please let me know how to... (5 Replies)
Discussion started by: sandy162
5 Replies
LEARN ABOUT DEBIAN
dh-exec
DH-EXEC(1) dh-exec DH-EXEC(1)
NAME
dh-exec - Debhelper executable file helpers
SYNOPSIS
#! /usr/bin/dh-exec
src/libfoo-*.so.* debian/foo-plugins/usr/lib/foo/${DEB_HOST_MULTIARCH}/
etc/example.conf => debian/foo/etc/foo/foo.conf
DESCRIPTION
dh-exec is a simple program, meant to be used as the interpreter for executable debhelper config files.
It is a wrapper around the various other sub-commands (see below), and will pipe the input file through all of them in turn, using an
ordering that makes most sense in the vast majority of cases.
The order as of now is dh-exec-subst gets run first, followed by dh-exec-install, so that variable expansion happens before files need to
be copied.
ARCHITECTURE
dh-exec is built up from three layers: there is the dh-exec utility, its single entry point, the only thing one will need to call.
Below that, there are the various sub-commands, such as dh-exec-subst, dh-exec-installs and dh-exec-illiterate, which are thin wrappers
around the various dh-exec scripts, that make sure they only run those that need to be run.
And the lowest layer are the various scripts that do the actual work.
One can control which sub-commands to run, or if even more granularity is desired, one can limit which scripts shall be run, too. See below
for the options!
OPTIONS
--with=command[,command ...]
Replace the list of sub-commands to run the input through with a custom list (where entries are separated by whitespace or commas).
This option will always replace the existing list with whatever is specified.
This can be used to explicitly set which sub-commands to use.
The list must not include the dh-exec- prefix.
Defaults to subst,install.
--without=command[,command ...]
Inversely to the option above, this lists all the sub-commands which should not be used.
The list must not include the dh-exec- prefix.
--with-scripts=script[,script ...]
Replace the list of scripts to run the input through with a custom list (where entries are separated by whitespace or commas). This
option will always replace the existing list with whatever is specified.
This can be used to explicitly specify which scripts to use, limiting even beyond what the --with option is capable of.
The list must not include the dh-exec- prefix.
By default it is empty, meaning there is no filtering done, and whatever scripts the sub-commands find, will be run.
--no-act
Do not really do anything, but print the pipeline that would have been run instead.
--list
List the available sub-commands and scripts, grouped by sub-command.
--help, --version
Display a short help or the package version, respectively.
SUB-COMMANDS
dh-exec-subst
Substitutes various variables (either from the environment, or from dpkg-architecture(1)).
dh-exec-install
An extension to dh_install(1), that supports renaming files during the copy process, using a special syntax.
ENVIRONMENT
DH_EXEC_LIBDIR
The directory in which the wrapped sub-commands reside. Defaults to /usr/lib/dh-exec/.
DH_EXEC_SCRIPTDIR
The directory in which the scripts that do the heavy work live. Defaults to /usr/share/dh-exec/.
FILES
$DH_EXEC_LIBDIR/dh-exec-*
The various sub-commands.
$DH_EXEC_SCRIPTDIR/dh-exec-*
The various scripts ran by the sub-commands.
SEE ALSO
debhelper(1), dh-exec-subst(1), dh-exec-install(1)
AUTHOR
dh-exec is copyright (C) 2011-2012 by Gergely Nagy <algernon@madhouse-project.org>.
2012-05-03 DH-EXEC(1)