06-03-2015
Thanks all - much easier than i thought!
Cheers
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am trying to load a group of files and their last dates modified into a text file that will in turn be used with SQL*Loader to load these files into Oracle. I am using a *.ksh script. I am getting the name of the file in by using the following:
for file_ext in 'cat loaddir.ext';
do
find... (2 Replies)
Discussion started by: akpopa
2 Replies
2. UNIX for Advanced & Expert Users
Hi,
I operate and use HF radars along the California coast for ocean surface currents. The devices use Mac OS as the control and logging software. The software generates thousands of files a week and while I've used PERL in the past to solve the problems of finding files I come to realize some... (6 Replies)
Discussion started by: dpath2o
6 Replies
3. UNIX for Advanced & Expert Users
Hi,
I am currently using the following command:
files=(ls enuCPU??.????.exp ntuCPU??.????.exp)
I need to now change the commmand to store the file names of files that have been modified before datetime equal to say '02/16/2008 20:30:00'
What could I use? (2 Replies)
Discussion started by: edisonantus
2 Replies
4. Shell Programming and Scripting
Hi,
I want to modify a filename in AIX by attaching the last modified timestamp. I want the timestamp completely in numerical format (eg:200905081210. yr-2009, mnth - 05, date -08, hr - 12, mins - 10).
For example if the filename is a.log and it was modified on April 6th 2008 at 21.00. I... (16 Replies)
Discussion started by: Ruks
16 Replies
5. UNIX for Dummies Questions & Answers
Hello all - I've looked and have not been able to find a "find" command that will list the last modified date of files within a specific directory and its subdirectories. If anyone knows of such a command it would be very much appreciated!
If possible, I would like to sort this output and have... (5 Replies)
Discussion started by: MichaelH3947
5 Replies
6. Shell Programming and Scripting
I need a unix command which will find all the files greater that a particular date in the file name.
say for example I have files like(filenaming cov : filename.YYDDMMSSSS.txt)
abc.201206015423.txt
abc.201207013456.txt
abc.201202011234.txt
abc.201201024321.txt
efg.201202011234.txt... (11 Replies)
Discussion started by: lijjumathew
11 Replies
7. Shell Programming and Scripting
I'm having problems with my bash script. I would like to find a file matching today's date in the filename, i.e. my_file_20120902.txt and then move it to a different directory, i.e. /tmp. Thanks. (1 Reply)
Discussion started by: jamesi
1 Replies
8. Shell Programming and Scripting
Hi,
We've a list of files that gets created on a weekly basis and it has got a date and time embedded to it. Below are the examples. I want to find out how to get the latest files get the date and time stamp out of it.
Files are
PQR123.PLL.M989898.201308012254.gpg... (1 Reply)
Discussion started by: rudoraj
1 Replies
9. UNIX for Dummies Questions & Answers
Hi i have two directories and files inside them
Directory 1:
Directory 2:
These files are the same but song.mp3 in Directory 1 is newer than song.mp3 in Directory 2, and work.txt in Directory 2 is newer than work.txt in Directory 1.
Now is my question. How i can compare these files... (10 Replies)
Discussion started by: Falstaff
10 Replies
10. UNIX for Dummies Questions & Answers
This should recursively walk through all dirictories and
search for a specified string in all present files, if found
output manicured content (eg some regex) with CAT into
a specified directory (eg /tmp/)
one by one, keeping the original names
This is what I have so far, which seems to... (1 Reply)
Discussion started by: lowmaster
1 Replies
LEARN ABOUT DEBIAN
dpatch.make
DPATCH.MAKE(7) dpatch DPATCH.MAKE(7)
NAME
dpatch.make - simplistic wrapper around dpatch(1) for make(1).
SYNOPSIS
include /usr/share/dpatch/dpatch.make
DESCRIPTION
For backwards compatibility and ease of use, dpatch.make is provided along with dpatch(1). Its purpose is to implement generic patch and
unpatch rules that can be reused in debian/rules scripts.
WARNING
dpatch is deprecated, please switch to the `3.0 (quilt)' Debian source package format instead. See http://wiki.debian.org/Projects/Deb-
Src3.0#FAQ for a short guide on how to do it.
USAGE
Using dpatch.make is rather straightforward: one has to include the file in debian/rules, change the appropriate targets to depend on patch
and unpatch, and that is all it takes.
Figuring out what the appropriate target is, requires some thought. Generally, one has a build target, or config.status, or configure (or
any of these with a -stamp suffix). Most of the time these are called first during the build, so one of these (the one that exists, and is
not depended upon by another one) has to be modified to depend on the patch target in dpatch.make.
Doing the same for the clean target is easier. One only has to rename the old rule to, say, clean-patched, then make a new one that has
clean-patched and unpatch in its list of prerequisites.
CUSTOMISATION
There are a few variables which are used by dpatch.make, which can be set before including it, in order to change the systems behaviour a
little.
These variables are:
DEB_SOURCE_PACKAGE
This is the name of the source package, used when creating the stamp file. By default, it is empty.
DPATCH_STAMPDIR
This is the directory where stamp files will be put. Default is debian/patched.
DPATCH_STAMPFN
The name of the stamp file, which contains the patch descriptions and other possible meta-data. Default value is patch-stamp.
DPATCH_PREDEPS
A list of make targets to call before applying the dpatch.
DPATCH_WORKDIR
The target directory to apply patches to. By default, it is the current directory.
PATCHLIST
The list of patches to apply. This is an alternative to debian/patches/00list - that is, if this variable is not empty, the
contents of 00list will be ignored, and this variable will be used instead.
EXAMPLE
include /usr/share/dpatch/dpatch.make
build: build-stamp
build-stamp: patch-stamp
${MAKE}
touch build-stamp
clean: clean1 unpatch
clean1:
${MAKE} clean
rm -rf debian/files debian/substvars debian/imaginary-package
.PHONY: patch unpatch ...
.
.
.
SIDE EFFECTS
Using dpatch.make instead of calling dpatch directly has one side effect: it will create a file called patch-stamp containing some
meta-information extracted from the scriptlets.
Depending on a phony patch target directly from build target may cause build target to be reevaluated even when there is no change to be
done. Instead, try making build-stamp depend on patch-stamp as specified in this example.
AUTHOR
Originally by Gergely Nagy. Modified by Junichi Uekawa.
SEE ALSO
dpatch(1), dpatch(7), dpatch-edit-patch(1), dpatch-list-patch(1), dpatch-convert-diffgz(1)
DPATCH 2 Dec 13 2011 DPATCH.MAKE(7)