i tried the following:-
sed -e file 's/^@//g' > temp
also tried
sed -e file 's///g' > temp
nothing happened....can someone please tell me wht is wrong???
also someinformation abt the character "^@"(it is ONLY ONE character and NOT TWO characters)
thanx in advance.. (13 Replies)
Hello and thx for reading this
I'm using sed to remove only the leading spaces in a file
bash-280R# cat foofile
some text
some text
some text
some text
some text
bash-280R#
bash-280R# sed 's/^ *//' foofile > foofile.use
bash-280R# cat foofile.use
some text
some text
some text... (6 Replies)
Can somebody explain why my sed command is not working.
I do the folloinwg:
Generates a binary file to /tmp/x1.out
/usr/lib/sa/sa2 -s 4:00 -e 8:00 -i 3600 -A -o /tmp/x1.out
decodes the file (no problem so far)
sar -f /tmp/x1.out
When I do this it does not appear to delete the... (4 Replies)
Hi,
I am new to Sed and would like to know if it is possible to remove the characters .
I have a couple of files with a keyword and would like to remove the substring.
I am Using sed s/// but Its not working
Thanks for your Support
Andrew Borg (2 Replies)
Hi All,
I have output like this below
ldprod/03
ldprod/02
ldprod/01
ldprod/00
ldnprod/
ldnprod/030
I want only remove all character including /
ldprod
ldprod
ldprod
ldprod
ldprod
ldnprod (8 Replies)
Hi I have the following kind of line sin my file .
print ' this is first'.
print ' this is firs and next '
' line continuous '. -- this is entire print line.
print ' this is first and next '
' line continuous and'
'still there now over'. -- this 3lines together a single print line.
... (5 Replies)
Hi all,
I have this input:
"203324780",,"89321213261247090146","VfdsD150","0D","fd3221","V0343","aaa","Direkt","fsa","2015.02.27","39833,54454,21214",,,"fd","NORMAL","D","10fd","1243 Flotta","HiĂĄnytalan","2013.02.25",,"2013.02.25","2013.02.24","2013.02.28",,"SajĂĄt... (4 Replies)
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)