01-29-2018
Welcome
KumarPiyush7225,
I have a few to questions pose in response first:-
- What OS, shell and version are you using?
- What logical process have you considered? (to help steer us to follow what you are trying to achieve)
- What are the rules for causing an alert? Is it simply the record being mentioned 3 or more times?
- What is the format of the Test.log file?
Looking at the code, for every record in
po_numbers you are reading the full
Test.log file. That is the target - reduce the number of times you read a huge file.
There are probably many ways to achieve most tasks, so giving us an idea of your style and thoughts will help us guide you to an answer most suitable to you so you can adjust it to suit your needs in future.
Kind regards,
Robin
10 More Discussions You Might Find Interesting
1. Programming
hi ,
i ve coded a C program
in that im using malloc dynamically ,
it is being called many times in the program
The program is to simulate jobs in manufacturing system.
the execution time is increasing drastically as the number of jobs are increased.
could any body tel what may be the problem... (2 Replies)
Discussion started by: ramki_rk
2 Replies
2. BSD
Say for instance, I would like to reduce the delay/waiting time for the boot-time menu from 10 seconds to 5 seconds, how would I go about doing it?
From what I've been able to find, entering "autoboot 5" into the right file would take care of that for me, but the man pages are unclear as to... (1 Reply)
Discussion started by: DownSouthMoe
1 Replies
3. UNIX for Dummies Questions & Answers
is there a command in Solaris 8 that will show a particular scripts last execution time? (1 Reply)
Discussion started by: cubs0729
1 Replies
4. UNIX for Advanced & Expert Users
Hi all,
do ny o u'll know how to set a particular execution time for a program???
for eg.:
--> during the execution of a file, i call a certain other function.
--> while calling this function, my comp hangs.
now is there ny way in which i can go to the nxt line of code by aborting the call... (7 Replies)
Discussion started by: VGR
7 Replies
5. Shell Programming and Scripting
Hi All,
The below script I run daily and it consumes 2 hours approx.
In this I am calling another script and executing the same twice.
Is the loop below the cause for the slow process?Is it possible to finetune the program so that it runs in a much faster way?
The first script:
#!/bin/ksh... (4 Replies)
Discussion started by: Sreejith_VK
4 Replies
6. Shell Programming and Scripting
HI ,
I have a list1 which consists of data that i have to search and a list2 which has the files that need to be searched .So basically i am using list1 on list2 to see if list1 data is present if found replace it .I have written the code using foreach loop for each list .This is taking the... (1 Reply)
Discussion started by: madhul2002
1 Replies
7. UNIX for Dummies Questions & Answers
how much time a particular command or shell script executed
there is any command to know this
thanks (5 Replies)
Discussion started by: tsurendra
5 Replies
8. Shell Programming and Scripting
DELETED. (0 Replies)
Discussion started by: vasuvv
0 Replies
9. Shell Programming and Scripting
hi all,
i have written the following script that does this work:
1. copy large logs files from one server to another.
2. then unzip this files and extraxt from these large https logs only those fields that are neccesary.
3. then archive the extracted logs to new files.
BUT the problem is... (7 Replies)
Discussion started by: arrals_vl
7 Replies
10. Shell Programming and Scripting
AFILENAME=glow.sh
FILENAME="/${AFILENAME}"
WIDTHA=$(echo ${FILENAME} | wc -c)
NTIME=0
RESULTS=$(for eachletter in $(echo ${FILENAME} | fold -w 1)
do
WIDTHTIMES=$(awk "BEGIN{printf... (5 Replies)
Discussion started by: SkySmart
5 Replies
LEARN ABOUT SUNOS
xfs_logprint
xfs_logprint(8) System Manager's Manual xfs_logprint(8)
NAME
xfs_logprint - print the log of an XFS filesystem
SYNOPSIS
xfs_logprint [ options ] device
DESCRIPTION
xfs_logprint prints the log of an XFS filesystem (see xfs(5)). The device argument is the pathname of the partition or logical volume con-
taining the filesystem. The device can be a regular file if the -f option is used. The contents of the filesystem remain undisturbed.
There are two major modes of operation in xfs_logprint.
One mode is better for filesystem operation debugging. It is called the transactional view and is enabled through the -t option. The
transactional view prints only the portion of the log that pertains to recovery. In other words, it prints out complete transactions
between the tail and the head. This view tries to display each transaction without regard to how they are split across log records.
The second mode starts printing out information from the beginning of the log. Some error blocks might print out in the beginning because
the last log record usually overlaps the oldest log record. A message is printed when the physical end of the log is reached and when the
logical end of the log is reached. A log record view is displayed one record at a time. Transactions that span log records may not be
decoded fully.
OPTIONS
-b Extract and print buffer information. Only used in transactional view.
-c Attempt to continue when an error is detected.
-C filename
Copy the log from the filesystem to the file filename. The log itself is not printed.
-d Dump the log from front to end, printing where each log record is located on disk.
-D Do not decode anything; just print data.
-e Exit when an error is found in the log. Normally, xfs_logprint tries to continue and unwind from bad logs. However, sometimes it
just dies in bad ways. Using this option prevents core dumps.
-f Specifies that the filesystem image to be processed is stored in a regular file at device (see the mkfs.xfs(8) -d file option).
This might happen if an image copy of a filesystem has been made into an ordinary file with xfs_copy(8).
-l logdev
External log device. Only for those filesystems which use an external log.
-i Extract and print inode information. Only used in transactional view.
-q Extract and print quota information. Only used in transactional view.
-n Do not try and interpret log data; just interpret log header information.
-o Also print buffer data in hex. Normally, buffer data is just decoded, so better information can be printed.
-s start-block
Override any notion of where to start printing.
-t Print out the transactional view.
SEE ALSO
mkfs.xfs(8), mount(8).
xfs_logprint(8)