Since this site solved my problems before, I am back for more (solutions)
I down load via a script every day a file that has the same name as the file of the day before. I want to move that file to its own directory like:
/archive/jul30
How do I capture the systems date in a script an... (2 Replies)
Hi,
How do you find the create date of a directory? I can see the modification date using ls -l but I'm looking for the create date.
Many thanks
Helen (2 Replies)
I need some help to complet the below script:
DATE1=`date "+%d"`
#DATE2=`expr $DATE1 - 1`
#DATE3=$DATE2`date "+%m%y"`
DATE4=`date "+%a"`
if ; then
DATE2=`expr $DATE1 - 3`
else
DATE2=`expr $DATE1 - 1`
fi (7 Replies)
Hi,
After checking all the UNIX threads, I am able to come up with a solution so far. I am working on a shell script where it moves the files to a certain directory. The conditions to check are
1) Check if the file exists in the current directory.
2) Check if the destination directory... (2 Replies)
Hi, I have a question, is there any way I can, when i create a directory, put the current date on it so that the directory name will be "name-current date"? just curious (3 Replies)
I am preparing a shell script to backup a few config files on a daily basis, with a retention of 30 days. Need some help with syntax/examples:
The shell script (running as cron) would require the following:
1. create a sub-directory within a specified (backup) directory, in the format... (3 Replies)
Hi guys,
I had a scenario...
1. I had to get the previous days date in yyyymmdd format
2. i had to create a file with Date inthe format yyyymmdd.txt format
both are different
thanks guys in advance.. (4 Replies)
I have requirment to get last date of previous month and the first date of previous 4th month:
Example:
Current date: 20130320 (yyyymmdd)
Last date of previous month: 20130228 (yyyymmdd)
First date of previous 4th month: 20121101 (yyyymmdd)
In my shell --date, -d, -v switches are not... (3 Replies)
Hi all,
i have a folder, with tons of files containing as following,
on /my/folder/jobs/
some_name_2016-01-17-22-38-58_some name_0_0.zip.done
some_name_2016-01-17-22-40-30_some name_0_0.zip.done
some_name_2016-01-17-22-48-50_some name_0_0.zip.done
and these can be lots of similar files,... (6 Replies)
I have a bash that downloads a list and if that list has data in it then a new main directory is created (with the date) with several subdirectories (example1, example2, example3). My question is in that list there are portion of specific file types (.vcf.gz) - identifier towards the end that have... (0 Replies)
Discussion started by: cmccabe
0 Replies
LEARN ABOUT HPUX
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)