10-02-2010
try it without the exec. See if anything returns.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I just set up an ftp server with Red Hat 5.2. I am doing the work, I'm baby stepping, but it seems like every step I get stuck. Currently, I'm trying to set up a crontab job, but I'm getting the following message: /bin/sh: /usr/bin/vi: No such file or directory. I see that vi exists in /bin/vi,... (3 Replies)
Discussion started by: kwalter
3 Replies
2. UNIX for Dummies Questions & Answers
Hi All,
Can somebody tell me the difference between /bin, /usr/bin, /sbin ?
Thanx in advance,
Saneesh Joseph (3 Replies)
Discussion started by: saneeshjose
3 Replies
3. Shell Programming and Scripting
Hey everyone,
A coworker of mine has written a csh script that starts with #!/usr/bin/csh -f. It's my understanding that the -f should skip the .cshrc and .login files, but here's the problem: In the script "line" is used, and I happen to have a "line" in my ~/bin. When the script is ran my... (4 Replies)
Discussion started by: effigy
4 Replies
4. UNIX for Dummies Questions & Answers
Hi!
All the basic linux commands, ie. echo, find, etc, are located in /bin. I have a couple of programs that have these commands pointed towards /usr/bin, ie, /usr/bin/echo (even though the actual 'echo' command is in /bin). How can I alias or redirect or link the /usr/bin to /bin just for this... (6 Replies)
Discussion started by: dancerat
6 Replies
5. Solaris
Hi gentlemen.
For what intended is the directory /usr/local/bin? In this directory are some script.
I don't understand how these scripts being in this directory are started.
Each time after registration of the user occurs start of these scripts. These scripts start applications. (7 Replies)
Discussion started by: wolfgang
7 Replies
6. OS X (Apple)
Q1. I understand that /usr/local/bin means I can install/uninstall stuff in here and have any chance of messing up my original system files or effecting any other users. I created this directory myself.
But what about the directory I didn't create, namely /Users/m/bin? How is that directory... (1 Reply)
Discussion started by: michellepace
1 Replies
7. Solaris
Hi Experts,
I found that the same commands(sort, du, df, find, grep etc.) exists in both dir.
What is the difference to use them?
i.e: to use xpg4/bin/grep and usr/bin/grep
My OS version is SunOS 5.10
Regards,
Saps (7 Replies)
Discussion started by: saps19
7 Replies
8. UNIX for Dummies Questions & Answers
...... (30 Replies)
Discussion started by: larry burns
30 Replies
9. UNIX for Beginners Questions & Answers
i am new player in linux
what does mean ">& and >&!" in script or command line?
thanks (4 Replies)
Discussion started by: abdossamad2003
4 Replies
LEARN ABOUT DEBIAN
dh-exec-install
DH-EXEC-INSTALL(1) dh-exec DH-EXEC-INSTALL(1)
NAME
dh-exec-install - Install (and possibly rename) files.
SYNOPSIS
#! /usr/bin/dh-exec
debian/default.conf => /etc/my-package/start.conf
usr/bin/*
DESCRIPTION
Being a sub-command of dh-exec(1), this program must not be ran directly, but through dh-exec, which automatically runs all available
sub-commands if run bare; or explicitly with dh-exec --with=install.
It is meant to be used for dh_install(1) files, and those alone. If it finds that its input is not such a file, it will do nothing, but
echo back the contents.
The purpose of the program is to extend dh_install(1)'s functionality, by allowing to specify a destination filename.
This can be accomplished by a special syntax: the " => " mark between a source and a destination means that the source file should be
installed with the specified destination name.
For obvious reasons, the source must not be a wildcard, and the destination in this case must be a file, and not a directory.
All other non-comment lines are left alone.
RESTRICTIONS
Due to the way executable scripts are called from debhelper(1), there is no way to know what options were used for the original
dh_install(1). This means, that the --sourcedir option of dh_install(1) will not work correctly when dh-exec-install is in use.
IMPLEMENTATION
Internally, the renaming happens by creating a temporary directory under debian/tmp/, and copying (or moving, if the source was under
debian/tmp/ to begin with) the file there, with the new name.
This is done this way to allow dh_install(1) to do the real copying, and allow its options to continue working, even when renaming is
involved.
The temporary directory is put under debian/tmp so that it will be cleaned by dh_prep(1) when the clean target gets to run. Thus, no extra
code is needed anywhere to clean up the renamed files.
ENVIRONMENT
DH_EXEC_SCRIPTDIR
Indicates which directory the command-specific scripts should be sought for. If not specified, scripts will be searched for in
/usr/share/dh-exec/.
FILES
$DH_EXEC_SCRIPTDIR/dh-exec-install-*
The various scripts for the higher-level program.
SEE ALSO
debhelper(1), dh-exec(1), dh_install(1)
AUTHOR
dh-exec-install is copyright (C) 2011-2012 by Gergely Nagy <algernon@madhouse-project.org>.
2012-05-03 DH-EXEC-INSTALL(1)