10 More Discussions You Might Find Interesting
1. AIX
Hi,
We have 2 lpars on p6 blade. One of the lpar is having 3 core cpu with 5gb memory running sybase as database. An EOD process takes 25 min. to complete.
Now we have an lpar on P7 server with entitled cpu capacity of 2 with 16 Gb memory and sybase as database. The EOD process which takes... (17 Replies)
Discussion started by: vjm
17 Replies
2. UNIX for Dummies Questions & Answers
hi I am having a performance issue with the following requirement
i have to create a permutation and combination on a set of three files
such that each record in each file is picked and the output is redirected in
a specific format but it is taking around 70 odd hours to prepare a
combination... (7 Replies)
Discussion started by: mad_man12
7 Replies
3. AIX
Hi Guys,
This is the situation I am in. Provide your views and input where should I start?
I have one P7 test server and a p520 production server. the job is taking pretty long on the P7 test server when compared to the P5 production server. below is the full detail.
Informix... (5 Replies)
Discussion started by: ithinksgreen
5 Replies
4. Shell Programming and Scripting
Hi All,
I have the following script which I use in Nagios to check the health of the applications, the problem with it is that the curl part ($TOTAL) does not return anything after running for 2-3 hrs, even though from command line the script runs fine but not from Nagios.
There are 17... (1 Reply)
Discussion started by: jacki
1 Replies
5. AIX
Gurus, i have process that runs 5 times a day.
it runs normally (takes about 1 hour) to complete in 3 runs
but it is takes about ( 3 hrs to complete) two times
So i need to figure out why it takes significanlty high time during
those 2 runs.
The process is a shell script that connect to... (2 Replies)
Discussion started by: mad_man12
2 Replies
6. UNIX for Advanced & Expert Users
In my C program i am using very large file(approx 400MB) to read parts of it frequently. But due to large file the performance of the program goes down very badly. It shows very high I/O usage and I/O wait time.
My question is, What are the ways to optimize or tune I/O on linux or how i can get... (10 Replies)
Discussion started by: mavens
10 Replies
7. AIX
Hi All,
I am getting a performance issue in expect5.43.0 library on IBM AIX 5.3. When I have used exp_fexpectv call for pattern matching with the expect string, the execution latency of the call is approximately 200 ms. In that way, I am able to complete only 4 or 5 transactions per... (2 Replies)
Discussion started by: ravindra_maddal
2 Replies
8. Shell Programming and Scripting
I want to read a file.
is it good to use File I/O or shell script??
which one is the best option? (1 Reply)
Discussion started by: vishwaraj
1 Replies
9. UNIX for Advanced & Expert Users
Hi,
on a linux server I have the following :
vmstat 2 10
procs memory swap io system cpu
r b w swpd free buff cache si so bi bo in cs us sy id
0 4 0 675236 39836 206060 1617660 3 3 3 6 8 7 1 1 ... (1 Reply)
Discussion started by: big123456
1 Replies
10. AIX
We have a AIX v5.3 on a p5 system with a poor performing Ingres database.
We added one CPU to the system to see if this would help. Now there are two CPU's.
with sar and topas -P I see good results: CPU usage around 30%
with topas I only see good results in the process output screen, the... (1 Reply)
Discussion started by: rein
1 Replies
JDRESOLVE(1) User Contributed Perl Documentation JDRESOLVE(1)
NAME
jdresolve - resolves IP addresses into hostnames
SYNOPSIS
jdresolve [-h] [-v] [-n] [-r] [-a] [-d <level>] [-m <mask>] [-l <line cache>] [-t <timeout>] [-p] [-s <number of
sockets>] [--database=<db path>] <LOG FILE>
jdresolve [--help] [--version] [--nostats] [--recursive] [--anywhere] [--debug=<level>] [--mask=<mask>] [--linecache=<line
cache>] [--timeout=<timeout>] [--sockets=<number of sockets>] [--database=<db path>] [--dbfirst] [--dbonly]
[--dumpdb] [--mergedb] [--expiredb=<hours>] [--unresolved] [--progress] <LOG FILE>
DESCRIPTION
jdresolve resolves IP addresses to hostnames. Any file format is supported, including those where the line does not begin with the
IP address. One of the strongest features of the program is the support for recursion, which can drastically reduce the number
of unresolved hosts by faking a hostname based on the network that the IP belongs to. DNS queries are sent in parallel, which means
that you can decrease run time by increasing the number of simultaneous sockets used (given a fast enough machine and available
bandwidth ). By using the database support, performance can be increased even further, by using cached data from previous runs.
OPTIONS
-h, --help
produces a short help message
-v, --version
display version information
-n, --nostats
don't display stats after processing
-r, --recursive
recurse into C, B and A classes when there is no PTR (default is no recursion)
-d, --debug=<debug-level>
debug mode - no file output, just statistics during run (verbosity level range: 1-3)
-t, --timeout=<seconds>
timeout in seconds for each host resolution (default is 30 seconds)
-l, --line-cache=<lines>
numbers of lines to cache in memory (default is 10000
-s, --sockets=<sockets>
maximum number of concurrent sockets (use ulimit -a to check the max allowed for your operating system - defaults to 64)
-m, --mask=<mask>
<mask> accepts %i for IP and %c for class owner, e.g. "somewhere.in.%c" or "%i.in.%c" (default is "%i.%c")
-a, --anywhere
resolves IPs found anywhere on a line (will resolve all IPs if there is more than one)
-p, --progress
prints a nice progress bar indicating the status of the resolve operations
--database=<db path>
path to database that holds resolved hosts/classes
--dbfirst
check if we have resolved entries in the database before sending out DNS queries
--dbonly
don't send DNS queries, use only resolved data in the database
--dumpdb
dumps a database to STDOUT
--mergedb
merges resolved IP/classes from a file (or STDIN) with a database
--expiredb=<hours>
expires entries in the database that are older than <hours> hours
--unresolved
won't attempt to resolve IPs, only lists those that were not resolved
<LOG FILE>
the log filename or '-' for STDIN
EXAMPLES
jdresolve access_log > resolved_log
jdresolve -r -s 128 access_log > resolved_log
jdresolve -r --database hosts.db access_log > res_log
SEE ALSO
rhost(1)
AUTHOR
jdresolve was written by John D. Rowell <me@jdrowell.com>, and is licensed under the terms of the GNU General Public License.
The original version of this man page was written by Craig Sanders <cas@taz.net.au>, for the Debian GNU/Linux package of jdresolve,
and is also licensed under the terms of the GNU GPL.
3rd Berkeley Distribution perl 5.005, patch 03 JDRESOLVE(1)