03-23-2013
Please use CODE tags!
If you don't show us the contents of MasterFile.txt and Pattern.txt, there isn't much we can do to figure out why your pipelines aren't working (although they could easily be made faster and more efficient by getting rid of the unneeded cat commands).
What system are you using. (Are you by any chance using any files produced on a Windows system with carriage return and newline characters at the end of each line instead of just a newline?)
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I 'm trying to grep 2 fieldds on 2 differnt lines. Like this:
psit > file
egrep -e '(NS|ES)' $file. Not working. If this succeeds then run next cmd else exit. Pls Help
Gundu (13 Replies)
Discussion started by: gundu
13 Replies
2. Shell Programming and Scripting
Hey guys:
I've been meaning to post this question for awhile...it is regarding grep. Let's say for example that the following entry is in logxx:
Wed Feb 2 07:44:11 <vsm> 91030 Line 5 Severity 1 Vps 6
Call Answered - DN:8753101 CLID:5164665761 PI:83
If I do a grep 91030... (27 Replies)
Discussion started by: cdunavent
27 Replies
3. Shell Programming and Scripting
Hi.
I have this format on a textfile:
VG Name /dev/vg00
PV Name /dev/dsk/c16t0d0
PV Name /dev/dsk/c18t0d0
PV Name /dev/dsk/c16t4d0
VG Name /dev/vg01
PV Name ... (6 Replies)
Discussion started by: jOOc
6 Replies
4. Shell Programming and Scripting
Guys I am having a problem with being able to find missing monitors in a configuration check script I am trying to create for accountability purposes for managing a large number of systems. What I am trying to do is run a script that will look at the raw config data in a file and pull all the pool... (7 Replies)
Discussion started by: scottzx7rr
7 Replies
5. UNIX for Dummies Questions & Answers
I want to search files (basically .cc files) in /xx folder and subfolders.
Those files (*.cc files) must contain #include "header.h" AND x() function.
I am writing it another way to make it clear,
I wanna list of *.cc files that have 'header.h' & 'x()'. They must have two strings, header.h... (2 Replies)
Discussion started by: ritikaSharma
2 Replies
6. UNIX for Dummies Questions & Answers
hi
i have kind of below text in a file.
I want to get a complete paragraph starting with START and ending with before another START) which has a particular string say XYZ or ABC
START XYZ hshjghkjh 45 ljkfd
fldjlj d jldf
START 3493u ABC 454
4545454
4545454 45454
4545454
START ...... (3 Replies)
Discussion started by: reldb
3 Replies
7. UNIX for Advanced & Expert Users
How do you grep 'select * from table_name' string from a script if the select * and from table_name are on 2 different lines ? like
select *
from table_name
Any help would be greatly appreciated !!!
Thanks
RDR (4 Replies)
Discussion started by: RDR
4 Replies
8. UNIX for Dummies Questions & Answers
I have 1300 files (SearchFiles0001.txt, SearchFiles0002.txt, etc.) , each with 650,000 lines, tab-delimited data.
I have a pattern file, with about 1000 lines with a single word. Each single word is found in the 1300 files once.
If I grep -f PatternFile.txt SearchFiles*.txt >OutputFile.txt... (2 Replies)
Discussion started by: newhavendweeb
2 Replies
9. UNIX for Dummies Questions & Answers
I want to grep multiple lines from a text file. I want to grep all lines containing X,Y and NA in a single command. How do I go about doing that?
This is what my text files look like:
rs1983866 0.0983 10 100016313
rs1983865 0.5994 X 100016339
rs1983864 0.3272 11 100017453
rs7077266... (2 Replies)
Discussion started by: evelibertine
2 Replies
10. Shell Programming and Scripting
Hi Everyone,
Im currently using the below code to pull data from a large CSV file and put it into smaller files with just the data associated with the number that I "grep".
grep 'M053' test.csv > test053.csv
Is there a way that I can use grep to run through my file like the example below... (6 Replies)
Discussion started by: TheStruggle
6 Replies
VIS(1) BSD General Commands Manual VIS(1)
NAME
vis -- display non-printable characters in a visual format
SYNOPSIS
vis [-cbflnostw] [-F foldwidth] [file ...]
DESCRIPTION
The vis utility is a filter for converting non-printable characters into a visual representation. It differs from 'cat -v' in that the form
is unique and invertible. By default, all non-graphic characters except space, tab, and newline are encoded. A detailed description of the
various visual formats is given in vis(3).
The options are as follows:
-b Turns off prepending of backslash before up-arrow control sequences and meta characters, and disables the doubling of backslashes.
This produces output which is neither invertible or precise, but does represent a minimum of change to the input. It is similar to
``cat -v''.
-c Request a format which displays a small subset of the non-printable characters using C-style backslash sequences.
-F Causes vis to fold output lines to foldwidth columns (default 80), like fold(1), except that a hidden newline sequence is used,
(which is removed when inverting the file back to its original form with unvis(1)). If the last character in the encoded file does
not end in a newline, a hidden newline sequence is appended to the output. This makes the output usable with various editors and
other utilities which typically do not work with partial lines.
-f Same as -F.
-l Mark newlines with the visible sequence '$', followed by the newline.
-n Turns off any encoding, except for the fact that backslashes are still doubled and hidden newline sequences inserted if -f or -F is
selected. When combined with the -f flag, vis becomes like an invertible version of the fold(1) utility. That is, the output can be
unfolded by running the output through unvis(1).
-o Request a format which displays non-printable characters as an octal number, ddd.
-s Only characters considered unsafe to send to a terminal are encoded. This flag allows backspace, bell, and carriage return in addi-
tion to the default space, tab and newline.
-t Tabs are also encoded.
-w White space (space-tab-newline) is also encoded.
SEE ALSO
unvis(1), vis(3)
HISTORY
The vis command appeared in 4.4BSD.
BUGS
Due to limitations in the underlying vis(3) function, the vis utility does not recognize multibyte characters, and thus may consider them to
be non-printable when they are in fact printable (and vice versa).
BSD
June 25, 2004 BSD