It's probably eating the backslash since perl double-quotes evaluate those. You may need to escape the escaping. You'll probably also need to escape those $ in your awk, since perl evaluates those into variables, and escape the double-quotes i the awk statement, so perl won't mistake them for its own.
I remember writing Perl like that: Line after line after line of nothing but system() and backticks. Eventually I noticed they were starting entire bourne shells just to parse one "mv a b" and was horrified -- by avoiding the shell I'd actually used eight of them consecutively
Returning much later, I rewrote some of these "perl" scripts as shell, making them much smaller, simpler, and saner.
Last edited by Corona688; 12-16-2011 at 03:48 PM..
Hello,
I create a file touch 1201093003 fichcomp
and inside a repertory (which hava a lot of files) I want to list all files created before this file :
find *.* \! -maxdepth 1 - newer fichcomp but this command returned bash: /usr/bin/find: Argument list too long
but i make a filter all... (1 Reply)
Hi,
Happy new year.
Would you be so kind to explain me what does this instruction :
find /rep/app -type l -exec ls -l {} \;> allink.lst
Many thanks. (2 Replies)
I am using csh and getting the error "find: No match." but I cannot figure out why. What I am trying to do is set the find command to a variable and then execute the variable as a command. I ran it through a debugger and it looks like $FIND is getting set but the find command can not actually be... (2 Replies)
Hi
I wish to find only files in dir /srv/container/content/imz06/. It means exclude subfolder /srv/container/content/imz06/archive/
> uname -a
SunOS testbox6 5.10 Generic_139555-08 sun4v sparc SUNW,Sun-Blade-T6320Its Solaris default "find"
> find /srv/container/content/imz06/* -name... (4 Replies)
This is a huge issue. and I need it fixed ASAP.
account-system gate-system race_traffic_sensor
achievement-system global race_voicepack
admin glue-system realdriveby
admin-system gps realism-system... (5 Replies)
Dear Perl's Users,
Could anyone help me how to solve my problem. I have data with details below.
TTY NAME SEQUENCES
U-0 UNIX 0
U-1 UNIX 1
U-2 UNIX 2 <-- From 2 jump to 5
U-5 UNIX 5
U-6 UNIX 6 <-- From 6 jump to 20
U-20 ... (2 Replies)
How can I recursively find all files in a directory and print out the file and first line number of any text blocks that match the below cases?
This would seem to involve find, xargs, *grep, regex, etc.
In summary, I want to find so-called empty "try-catch blocks" that do not contain code... (0 Replies)
Guys,
I want to find the log files greather than 23 days and i want to perform 2 things here.
one is to list the files and second is to gzip the files. hope this can be done using sh -c option. but not sure the exact command.
find . -name "*.log" -mtime +23 -exec ls -la {} \;
... (5 Replies)
this find command works when using manually on the command line
--
$ ls -latr file*.log
-rw-r--r-- 1 oracle dba 75 Jan 4 05:00 file_2.log
-rw-r--r-- 1 oracle dba 75 Jan 4 05:00 file_1.log
$
$ find . ! -name -prune -type f -name "file*.log" -daystart -mtime 2
./file_1.log
./file_2.log
$... (8 Replies)
Discussion started by: wtolentino
8 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)