10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello all,
I'm working on a general script for something at work. I'm an up-and-comer backup for a Shell Scripter this company has had for 35 years lol. Anyway, I have a config file I'm trying to pull Variables from as the Config File is used for multiple scripts. Does the below make sense and... (7 Replies)
Discussion started by: phunk
7 Replies
2. Programming
Hi friends,
I hope everyone is doing fine. I have this confusion, hope you can help me out with it. The header files contain only function prototypes. Where are the function definitions located. For example, if I would like to see how printf works, where can I see its definition, stdio.h only... (2 Replies)
Discussion started by: gabam
2 Replies
3. Solaris
Are the default password setting parameters (that are in /etc/login.defs) only used when a new local account is created on a server?
It looks to me like a 'useradd userid1' command will look to the /etc/login.defs file to get default values for MINWEEKS MAXWEEKS and PASSLENGTH. If the parms are... (2 Replies)
Discussion started by: msdjunk
2 Replies
4. Shell Programming and Scripting
Hi, I am a german lawstudent and have to learn a few hundred definitions and laws in the next months. I thought it would be cool to have a little helper, a bashscript which is working with flat textfiles. I found one in the archlinuxforum which was almost perfect...almost. It is on some point based... (2 Replies)
Discussion started by: phr0st
2 Replies
5. UNIX for Dummies Questions & Answers
Just wondering: Can anyone tell me what is meant by the term 'interactive shell" or 'built-in commands' - for example, if I type 'man set' I get a page listing all the 'built in commands' but no explanation of what they are as a concept or what they do.
And while I'm here: I was wondering as... (5 Replies)
Discussion started by: Straitsfan
5 Replies
6. UNIX for Dummies Questions & Answers
What is the difference between the(a) shell and the (a) command-line interpreter?
Here we're talking about the complete dummy question, but could someone point me right.
(yes, have written scripts in for instance bash shell,
and and grepp-ed my way around ....:eek: (4 Replies)
Discussion started by: amkgw
4 Replies
7. Shell Programming and Scripting
I setup alias on my .bash_profile. It works very will until I did another sh on command prompt. I typed alias on new shell and all the definitions did not carry over. How to correct this? Thanks in advance. (9 Replies)
Discussion started by: wangzosen
9 Replies
8. Shell Programming and Scripting
Hello, All :) ...I just figured out how to setup a function definitions file for bc...I was going to create lots more functions for it, but I'll bet that a huge file with tons of definitions has already been written...?
Thanx in advance for any replies,
Pudnik (0 Replies)
Discussion started by: Pudnik
0 Replies
9. UNIX for Advanced & Expert Users
Hi there,
Does anyone know of a place that will give details for each of the following UDP parms? I've found documentation on there size limits but not what they will do or affect if changed.
udp_xmit_hiwat
udp_xmit_lowat
udp_recv_hiwat
udp_max_buf ... (1 Reply)
Discussion started by: nhatch
1 Replies
10. Linux
Hi.
How do I enter and escape from graphics mode on RedHat Linux to capture escape sequences. I'm trying to edit the system termcap. (2 Replies)
Discussion started by: cstovall
2 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)