syntax error The source line is 12.
The error context is
retval=$(sqlplus -s abc/abc >f
awk: The statement cannot be correctly parsed.
The source line is 12.
syntax error The source line is 13.
Please advise
Last edited by COD; 04-18-2008 at 04:39 PM..
Reason: incorrect info
Hi Guys,
I spend half a day getting this to work with no luck, perhaps you guys can help..
I have a string from a file looking like this:
module::name=test::type=generic_data::exec=snmpget.......::desc=A Little Test::interval=300
what I would like to split it, so I get a value for each... (3 Replies)
Hi,
I have a directory file name:
/auto/space/user/jen/CED/CED_01MZ/visit1/DCE_2eco/016/echo1
I would like to just get the following outputs into variables such that:
variable1 = /auto/space/user/jen/CED/CED_01MZ/visit1/
and
variable2 = DCE_2eco/016/echo1
I've tried it with... (2 Replies)
hi guys,
i want to parse a file using public function, the file contain raw data in the below format i want to get the output like this to load it to Oracle DB
MARWA1,BSS:26,1,3,0,0,0,0,0.00,22,22,22.00
MARWA2,BSS:26,1,3,0,0,0,0,0.00,22,22,22.00
this the file raw format:
Number of... (6 Replies)
Hi,
I would like to parse the next output of an lvdisplay -v using awk:
--- Logical volumes ---
LV Name /dev/vg01/lvol3
VG Name /dev/vg01
LV Permission read/write
LV Status available/syncd
Mirror copies ... (2 Replies)
Hi folks,
I have XML files with the following sections (section occurs once per file) in them:
<AuthorList CompleteYN="Y">
<Author ValidYN="Y">
<LastName>Bernal</LastName>
<ForeName>Federico</ForeName>
... (3 Replies)
Hi guys (and gals).
I need some help. I'm running an IVR purely on Asterisk where I capture the DTMFs. After pulsing each DTMF I have Asterisk write to a file with whatever was dialed (mostly used for record-keeping) and at the end of the survey I write all variables in a single line to a... (2 Replies)
Hi Experts,
I am trying to parse the following file;
FILEA
a|b|c|c|c|c
a|b|d|d|d|d
e|f|a|a|a|a
e|f|b|b|b|boutput expected:
a<TAB>b
<TAB><TAB>c<TAB>c<TAB>c<TAB>c<TAB>
<TAB><TAB>d<TAB>d<TAB>d<TAB>d<TAB>
e<TAB>f
<TAB><TAB>a<TAB>a<TAB>a<TAB>a<TAB>
<TAB><TAB>b<TAB>b<TAB>b<TAB>b<TAB>*... (7 Replies)
Output of the below code includes unmatched date.Please correct it
df -k|awk '$4>50 {print $1, "\t"$4,"\t" $7}'
It gives output less than 50% also. (5 Replies)
Hi all, I have a file that contains a good hundred of these job definitions below:
Job Name Last Start Last End ST Run Pri/Xit
________________________________________________________________ ____________________... (7 Replies)
Discussion started by: atticuss
7 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)