Hello, using date, we can easily get today's date
$ date +%y-%m-%d
06-12-08
is it possible for me to get yesterday's date using 'date', if not, is there any quick and easy way to do that?
Thanks! (1 Reply)
I am not using GNU nor BSD. On AIX, how do you return yesterday in the format of i.e. "May 09" with a space.
# `TZ=y380 date +%h""%d`
>> May09
# `TZ=y380 date +%h" "%d`
>> May
I appreciate your help in advance.
thx (3 Replies)
I haven't been using linux very long( and when I say that its only been about 1 week for me) I was told to do the following:
Create a Bash script that will copy all the files and subdirectories in one directory to a newly created directory. You may name the receiving directory anything you like.... (4 Replies)
I was playing to find a simple way to get yesterday's date, and came up with this (on an AIX 5.2 box):
$ date
Thu Feb 19 11:21:26 EST 2009
$ echo $TZ
EST5EDT
$ yesterday=`TZ=$(date +%Z)+24 date`
$ echo $yesterday
Wed Feb 18 16:21:52 GMT 2009
Why it is converted to GMT instead of... (2 Replies)
Hi,
`date` command will give the current days date.
Is there any command to get the previous day date?
I need the previous day value in my script.
Ahamed. (1 Reply)
HI All,
I am trying so long to find the yesterday's date to run a script but i failed
kinldy share the command to find yesterday's date in ksh
i tried with
date --date='1 day ago'
but it displaying error
your help will highly apeerciated.
Thanks (7 Replies)
Hi Friend,
i am using OS
HP-UX vvftf320 B.11.11 U 9000/800 511076331 unlimited-user license
now i have used below command but it giving today's date. i need your help to get yesterdate. Please correct me.
date +"%d%m%Y%H%M%S" -d "1 days ago
Thanks in advance,
Jewel (3 Replies)
Discussion started by: Jewel
3 Replies
LEARN ABOUT DEBIAN
bup-margin
bup-margin(1) General Commands Manual bup-margin(1)NAME
bup-margin - figure out your deduplication safety margin
SYNOPSIS
bup margin [options...]
DESCRIPTION
bup margin iterates through all objects in your bup repository, calculating the largest number of prefix bits shared between any two
entries. This number, n, identifies the longest subset of SHA-1 you could use and still encounter a collision between your object ids.
For example, one system that was tested had a collection of 11 million objects (70 GB), and bup margin returned 45. That means a 46-bit
hash would be sufficient to avoid all collisions among that set of objects; each object in that repository could be uniquely identified by
its first 46 bits.
The number of bits needed seems to increase by about 1 or 2 for every doubling of the number of objects. Since SHA-1 hashes have 160 bits,
that leaves 115 bits of margin. Of course, because SHA-1 hashes are essentially random, it's theoretically possible to use many more bits
with far fewer objects.
If you're paranoid about the possibility of SHA-1 collisions, you can monitor your repository by running bup margin occasionally to see if
you're getting dangerously close to 160 bits.
OPTIONS --predict
Guess the offset into each index file where a particular object will appear, and report the maximum deviation of the correct answer
from the guess. This is potentially useful for tuning an interpolation search algorithm.
--ignore-midx
don't use .midx files, use only .idx files. This is only really useful when used with --predict.
EXAMPLE
$ bup margin
Reading indexes: 100.00% (1612581/1612581), done.
40
40 matching prefix bits
1.94 bits per doubling
120 bits (61.86 doublings) remaining
4.19338e+18 times larger is possible
Everyone on earth could have 625878182 data sets
like yours, all in one repository, and we would
expect 1 object collision.
$ bup margin --predict
PackIdxList: using 1 index.
Reading indexes: 100.00% (1612581/1612581), done.
915 of 1612581 (0.057%)
SEE ALSO bup-midx(1), bup-save(1)BUP
Part of the bup(1) suite.
AUTHORS
Avery Pennarun <apenwarr@gmail.com>.
Bup unknown-bup-margin(1)