Parsing text file and feeding it into an executable
Hello, everyone. I am working wtihin AIX 5.3, and I need to do the following:
read the each line of file BASE.txt
do XK {line contents}
if XK's output begins with "BASE", then append line contents to file "output.txt"
continue until end of file
Here is what I tried(unsuccessfuly):
Basically, I need to end up with a list of entries from the "BASE.txt" file that returned 'BASE' as the first four characters, when used as an argument in the "XK" executable. The script I have returns only this:
ksh: syntax error: `done' unexpected
I know I am making this too difficult. Can you guys please help?
Hey Guys.I am a newbie on Bash Shell Scripting and Perl.And I have a question about file parsing.
I have a log file which contains reports about a communication device.I need to take some of the reports from the log file.Its hard to explain the issue.but shortly I can say that, the reports has a... (2 Replies)
Hi,
I need some help in extracting the Exception block between the lines
21 Feb 01:18:54:146 ERROR com.orbits.frameworks.integrationframework.ValidationException - Caught exception in validateRequest() (PID=565584)
and
21 Feb 01:18:55:149 INFO ... (0 Replies)
Any ideas?
1)loop through text file
2)extract everything between SOL and EOL
3)output files, for example: 123.txt and 124.txt for the file below
So far I have: sed -n "/SOL/,/EOL/{p;/EOL/q;}" file
Here is an example of my text file.
SOL-123.go
something goes here
something goes... (0 Replies)
The binary file is
ELF-64 executable object file - IA64.
How i know that the source is
Is there any comamnd in unix i can read these kind of files or use a thirty party software?
Thanks for your help (8 Replies)
Hi everyone,
I'm having trouble figuring this one out. I have ~100 *.fa files with multiple lines of fasta sequences like this: file1.fa
>xyzsequence
atcatgcacac......
ataccgagagg.....
atataccagag.....
>abcsequence
atgagatatat.....
acacacggd.....
atcgaacac....
agttccagat....
The... (2 Replies)
I'm new to scripting and was wondering if there was a way to accomplish what I want below using shell script(s).
If there is a log file as follows, where the id is the unique id of a process, with the timestamp of when the process began and completed displayed, would it be possible to find the... (3 Replies)
I was trying to parse the text file, which will looks like this
###XYZABC####
############
int = 4
char = 1
float = 1
.
.
############
like this my text file will contains lots of entries and I need to store these entries in the map eg. map.first = int and map.second = 4 same way I... (5 Replies)
I'm totally stumped with how to handle this huge text file I'm trying to deal with. I really need some help!
Here is what is looks like:
ab1ba67c331a3d731396322fad8dd71a3b627f89359827697645c806091c40b9
0.2
812a3c3684310045f1cb3157bf5eebc4379804e98c82b56f3944564e7bf5dab5
0.6
0.6... (3 Replies)
Hi Friends,
I am back for the second round today - :D
My input text file is this way
Home
friends
friendship meter
Tools
Mirrors
Downloads
My Data
About Us
Help
My own results
BLAT Search Results
ACTIONS QUERY SCORE START END QSIZE IDENTITY CHRO STRAND ... (7 Replies)
Discussion started by: jacobs.smith
7 Replies
LEARN ABOUT HPUX
packingrules
packingrules(4) Kernel Interfaces Manual packingrules(4)NAME
packingrules - packing rules file for cachefs
DESCRIPTION
is a packing rules file for packingrules contains a list of directories and files that are to be packed. It also contains a list of direc-
tories and files that are to be specifically excluded from packing. See cachefspack(1M).
Many users choose to manually create the packing rules file and edit it by hand. Users can edit the packingrules (using any editor) to
permanently change the packingrules file, or to gain access to more powerful options that are not available from the command line (such as
the command). It is much easier to enter complex wildcard expressions by editing the packingrules file.
Following is a description of the lines in a packing rules file. Blank lines and lines that begin with a pound sign are ignored. Lines
can be continued by placing a backslash () immediately before the newline character. All other lines in the packingrules file have one
of the following formats:
This line identifies a directory (or pair of directories)
under which files should be packed. At least one directory name must be specified. The arguments must be fully qualified
path names and may include environment variables.
This line enumerates a list of files and subdirectories
beneath the current directory to be packed. This specification is recursive. That is, specifying the name of a directory
automatically includes all files and subdirectories it contains.
This line enumerates a list of files that are not to be packed.
Regular expressions are permitted.
There are important differences between the arguments to the and the statements. The arguments to statements can contain slashes and are
interpreted as file names relative to the directories. The arguments to statements are simpler names or expressions that cannot contain
slashes. An statement will not override a LIST statement. statements only exclude files that are found beneath listed directories.
If the first name argument to a or an statement begins with an exclamation point the remainder of the statement will be executed as a com-
mand that will be run in the current directory. The output of the command will be treated as a list of newline separated file names to be
packed command) or to be excluded from the packing list command). For the command, the resulting file names will be interpreted relative
to the enclosing directory.
Blanks can be embedded in an argument by escaping them with a backslash () or enclosing the argument in double quotes (` " '). Double
quotes can be passed in arguments by escaping the double quotes with a backslash ().
lines only apply to the statement that precedes them. lines can appear before any statement (in which case they apply to all or after a
statement (in which case they only apply to the that precedes them). Any number of these statements can occur in any combinations. The
order is not important.
EXAMPLES
The use of these statements is illustrated in the following packing rules file.
#
# Ignore junk files.
#
IGNORE core *.o *.bak *%
#
# Pack everything in the work subdirectory and in a few
# favorite mailboxes.
#
BASE /net/bigserver/export/home/myname
LIST work
LIST m/incoming
LIST m/action
LIST m/pending
#
# Pack two important project directories but skip
# all postscript output.
#
BASE /net/bigserver/export/projects $HOME/projects
LIST poindexter epiphany
IGNORE *.ps
#
# Pack the foonly package.
#
BASE /net/bigserver/opt/foonly /opt/foonly
LIST !cat .packinglist
#
# Also pack the latest executables for the standard
# build environment.
#
BASE /net/bigserver/export/buildenv $HOME/buildenv
LIST !find . -type f -a -perm -111 -a -print
AUTHOR
was developed by Sun Microsystems, Inc.
SEE ALSO cachefspack(1M).
packingrules(4)