08-16-2007
Thanks for the follow up.
I had one more option of doing that.
Just tried with few records and that seems to be better.
Actually I didnt compare with bulk number of records.
Will do that and post the results positively by end of tomorrow !
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
My product have around 10-15 programs/services running in the sun box, which together completes a task, sequentially. Several instances of the each program/service are running in the unix box, to manage the load and for risk-management reasons. As of now, we dont follow a strict strategy in... (2 Replies)
Discussion started by: Deepa
2 Replies
2. Filesystems, Disks and Memory
I have some questions regarding disk perfomance, and what I can do to make it just a little (or much :)) more faster.
From what I've heard the first partitions will be faster than the later ones because tracks at the outer edges of a hard drive platter simply moves faster. But I've also read in... (4 Replies)
Discussion started by: J.P
4 Replies
3. Shell Programming and Scripting
How would one go about optimizing this current .sh program so it works at a more minimal time. Such as is there a better way to count what I need than what I have done or better way to match patterns in the file? Thanks,
#declare variables to be used.
help=-1
count=0
JanCount=0
FebCount=0... (3 Replies)
Discussion started by: switch
3 Replies
4. OS X (Apple)
Hi forum,
I'm administrating a workstation/server for my lab and I was wondering how to optimize OSX. I was wondering what unnecessary background tasks I could kick off the system so I free up as much memory and cpu power.
Other optimization tips are also welcome (HD parameters, memory... (2 Replies)
Discussion started by: deiphon
2 Replies
5. Shell Programming and Scripting
Hi,
I have two files in the format listed below. I need to find out all values from field 12 to field 20 present in file 2 and list them in file3(format as file2)
File1 :
FEIN,CHRISTA... (2 Replies)
Discussion started by: nua7
2 Replies
6. Shell Programming and Scripting
Can this awk statement be optimized? i ask because log.txt is a giant file with several hundred thousands of lines of records.
myscript.sh:
while read line
do
searchterm="${1}"
datecurr=$(date +%s)
file=$(awk 'BEGIN{split(ARGV,var,",");print var}' $line)
... (3 Replies)
Discussion started by: SkySmart
3 Replies
7. Shell Programming and Scripting
I have a huge log file close to 3GB in size.
My task is to generate some reporting based on # of times something is being logged.
I need to find the number of time StringA , StringB , StringC is being called separately.
What I am doing right now is:
grep "StringA" server.log | wc -l... (4 Replies)
Discussion started by: Junaid Subhani
4 Replies
8. Shell Programming and Scripting
Hello,
I'm looking for advice on how to optimize this bash script, currently i use the shotgun approach to avoid file io/buffering problems of forks trying to write simultaneously to the same file. i'd like to keep this as a fairly portable bash script rather than writing a C routine.
in a... (8 Replies)
Discussion started by: f77hack
8 Replies
9. Shell Programming and Scripting
now, i have to search for a pattern within a particular time frame which the user will provide in the following format:
19/Jun/2018:07:04,21/Jun/2018:21:30
it is easy to get tempted to attempt this search with a variation of the following awk command:
awk... (3 Replies)
Discussion started by: SkySmart
3 Replies
10. Web Development
Yes.
Got few suggestions.
- How about minifying resources
- mod_expires
- Service workers setup
https://www.unix.com/attachments/web-programming/7709d1550557731-sneak-preview-new-unix-com-usercp-vuejs-demo-screenshot-png (8 Replies)
Discussion started by: Akshay Hegde
8 Replies
TRPT(8) BSD System Manager's Manual TRPT(8)
NAME
trpt -- transliterate protocol trace
SYNOPSIS
trpt [-a] [-f] [-j] [-p hex-address] [-s] [-t] [system [core]]
DESCRIPTION
The trpt utility interrogates the buffer of TCP trace records created when a socket is marked for ``debugging'' (see setsockopt(2)), and
prints a readable description of these records. When no options are supplied, trpt prints all the trace records found in the system grouped
according to TCP connection protocol control block (PCB).
The following options may be used to alter this behavior:
-a In addition to the normal output, print the values of the source and destination addresses for each packet recorded.
-f Follow the trace as it occurs, waiting a short time for additional records each time the end of the log is reached.
-j Just give a list of the protocol control block addresses for which there are trace records.
-p Show only trace records associated with the protocol control block at the given address hex-address.
-s In addition to the normal output, print a detailed description of the packet sequencing information.
-t In addition to the normal output, print the values for all timers at each point in the trace.
The recommended use of trpt is as follows. Isolate the problem and enable debugging on the socket(s) involved in the connection. Find the
address of the protocol control blocks associated with the sockets using the -A option to netstat(1). Then run trpt with the -p option, sup-
plying the associated protocol control block addresses. The -f option can be used to follow the trace log once the trace is located. If
there are many sockets using the debugging option, the -j option may be useful in checking to see if any trace records are present for the
socket in question.
If debugging is being performed on a system or core file other than the default, the last two arguments may be used to supplant the defaults.
FILES
/boot/kernel/kernel
/dev/kmem
DIAGNOSTICS
no namelist When the system image does not contain the proper symbols to find the trace buffer; others which should be self explanatory.
SEE ALSO
netstat(1), setsockopt(2)
HISTORY
The trpt utility appeared in 4.2BSD.
BUGS
Should also print the data for each input or output, but this is not saved in the trace record.
The output format is inscrutable and should be described here.
BSD
December 11, 1993 BSD