When -depth is not used, the find command visits a directory before its contents. So, when find sees ab, it performs the -exec and afterwards tries to descend into ab to see what's there. That's where the error message comes from.
You could use -prune to prevent the descent.
Regards,
Alister
These 2 Users Gave Thanks to alister For This Post:
This is my list of sed commands: can anyone tell me where im going wrong. The script works on a file called data which contains 6 student id's and there answers for 6 questions.
!/bin/sh
sed -e 's/*//g' \ #replace * with nothing
-e s/ /X/g' \ #replacing empty space with X
-e... (2 Replies)
When I execute this line at the command prompt I get a different answer than when I run it in a script? Any ideas on how to resolve? I'm trying to find all files/dir in a directory except files that start with the word file.
Once I get this command to work, I will add the "delete" part to the... (6 Replies)
I need to find whether there is a file named vijay is there or not in folder named "opt" .I tried "ls *|grep vijay" but it showed permission problem.
so i need to use find command (6 Replies)
Hi guys.
I am trying, to move files found with the find command...
Script runs fine, until it reaches a file that contains spaces...
Here is what i wrote up quickly.
ROOTDIR=/apps/data
SEARCH=$(find /data/HDTMPRestore/home/tmq/ -type f -print | grep Mods/Input/bck | cut -c19-)
for i... (1 Reply)
Hi,
How do you echo something once when a find statement returns null results?
This is when using mutiple locations and mutiple arguments.
The below find command the inner loop of a nested for loop where the outter loop holds the $args and the inner loop holds the locations.
find... (2 Replies)
Hi all!
I've faced with very unintelligible error using find/grep like this:
root@v29221:~# find /var/www/igor/data/www/lestnitsa.ru | grep u28507I get nothing as a result, but:
root@v29221:~# grep u28507 /var/www/igor/data/www/lestnitsa.ru/_var.inc
$db_name = 'u28507';... (2 Replies)
I am writing a script below, which has 2 loops. The outer one reads file sufffixed with a number and inner inside which loop through each line of the file and display each space delimited string. However, i find that the string printed out in the inner loop includes not only the delimited string in... (2 Replies)
I am trying to find the home directory of users on a UNIX (Solaris/AIX) box using
echo ~usernameThis does return the home directory for all valid users. For some reason this command also outputs home directory which are non-existent for few users who seem not to have logon access to that... (31 Replies)
Under one of my directories on server I have more than 500 files with different type and name. When I run the find command to list the files with 'ABC_DEFGH' in the begining of its name and older than 20 days, nothing is return as result. Though I know there are more than 400 files which their name... (10 Replies)
How to get a file 'zlib.h' in an entire directory with an excluded directory specified lives under that starting directory by using find command, as it failed on:
$ find . -name 'zlib.h' -a -ipath 'CHROME.TMP' -prune -o -print
it'll just list entirely up (2 Replies)
Discussion started by: abdulbadii
2 Replies
LEARN ABOUT DEBIAN
dh_installinit
DH_INSTALLINIT(1) Debhelper DH_INSTALLINIT(1)NAME
dh_installinit - install init scripts and/or upstart jobs 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, as well as upstart
job files into package build directories.
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.
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
If this exists, it is installed into etc/init/package.conf in the package build directory.
OPTIONS -n, --noscripts
Do not modify postinst/postrm/prerm scripts.
-o, --onlyscripts
Only modify postinst/postrm/prerm scripts, do not actually install any init script, default files, or upstart job. May be useful if the
init script or upstart job is shipped and/or installed by upstream in a way that doesn't make it easy to let dh_installinit find it.
-R, --restart-after-upgrade
Do not stop the init script until after the package upgrade has been completed. This is different than the default behavior, which
stops 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.
-r, --no-restart-on-upgrade
Do not stop init script on upgrade.
--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.
-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 will be passed to update-rc.d(8).
--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>
9.20120909 2012-04-10 DH_INSTALLINIT(1)