Hi
I would like to know wheather there is anyway to pass a variable to grep argument like this
grep "$myvar" $myfile
i would put this in a function and then call this function by setting different values to myvar and myfile.
is this possible at all.
regards
Hrishy (4 Replies)
I have a large file that I am grepping to find a certain string.
grep 'C:\Data\Directory\Test.txt' test.txt
It can not find it even though I know it is in there . I know that there is a problem with the backslashes but I can't get it to work. I tried
grep... (2 Replies)
Hi there, this is a very simple question.
When I do grep -c "PWD" filename, I get 5. This means the filename contains 5 lines of "PWD" occurence.
I tried to assign to a variable. int= grep -c "PWD" filename
When I typed echo $int
The output:
5
I get an empty line space. Now I... (1 Reply)
I have a problem. Suppose I have a log named transport.log
>>
tp finished with return code: 203
meaning:
wrong syntax in tp call
....
tp finished with return code: 0
meaning:
Everything ok.
<<
What i want to do is to get the return code of the 1st one. So I would probably do:... (2 Replies)
Changed Problem its a sed actually...
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
Use a sed command to create an output file from the input file. The input... (2 Replies)
Hi
I am trying to grep a string in a directory which is having 5000 files.
PA>> grep -iH 'linc.unisure_pr13n' *
bash: /usr/bin/grep: Arg list too long
I am getting the error. i also tried
PA>> ls -ltr | grep -iH 'linc.unisure_pr13n' *
but still i am getting the error
Please Advice... (4 Replies)
Hi everyone
i am facing a strange problem in grep below is the code
RC=0
grep $ERROR_MASK $LOG_FILE 2>&1 > /dev/null && RC=1 || RC=0
what does the above statment do i mean it search for error mask into log file and redirect the error to console null then what's the meaning of RC=1 ||... (2 Replies)
I have the following ksh
#!/bin/ksh
file=$OBS_APP_PATH/config/com/uhg/obs/inbound/configs/XMLFile_ServiceFeeDetail.xml
echo $file
cntWrd=0
echo $cntWrd
cntWrd= grep -c '<serviceFee>' $file
echo $cntWrd
while executing the above im getting the following error msg:... (2 Replies)
Hello. I'm learning shell scripting right now and I'm trying simple scripts. I have a problem with the one below. The idea is to found the number of files containing asd in their name. Here's the code:
#!/bin/sh
pattern=asd
total=0
for f in *
do
&& continue
if grep $pattern $f >... (3 Replies)
I don't know if you guys get this problem sometimes at Terminal but I had been having this problem since yesterday :( Maybe I overdid the Terminal. Even the codes that used to work doesn't work anymore.
Here is what 's happening:
* I wanted to remove lines containing digits so I used this... (25 Replies)
Discussion started by: Nexeu
25 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)