tcpdmatch man page on HP-UX

Man page or keyword search:  
man Server   10987 pages
apropos Keyword Search (all sections)
Output format
HP-UX logo
[printable version]

tcpdmatch(1)							  tcpdmatch(1)

NAME
       tcpdmatch - evaluate tcp wrapper service requests

SYNOPSYS
       inet_conf] daemon client

       inet_conf] daemon[[userclient

DESCRIPTION
       predicts	 how  the tcp wrapper would handle a specific request for ser‐
       vice.  Examples are given below.

       The program examines the access control tables (default and and	prints
       its  conclusion.	 For maximum accuracy, it extracts additional informa‐
       tion from the configuration file.

       When finds a match in the access	 control  tables,  it  identifies  the
       matched	rule.  In addition, it displays the optional shell commands or
       options in a printable format.  The display helps you find any discrep‐
       ancies  between	what you want and what understands for the access con‐
       trol rules.

   Arguments
       The daemon and client arguments are always required.

       daemon	 A daemon process name.	 Typically, the last  component	 of  a
		 daemon executable pathname.

       client	 A  host  name	or network address, or one of the `unknown' or
		 `paranoid' wildcard patterns.

		 When a client host name is specified, gives a prediction  for
		 each address listed for that client.

		 When  a  client  address is specified, predicts what would do
		 when the client name lookup fails.

       Optional information specified with the form:

       server	 A host name or network address, or one of  the	 `unknown'  or
		 `paranoid'  wildcard  patterns.   The	default server name is
		 `unknown'.

       Optional information specified with the form:

       user	 A client user	identifier.  Typically,	 a  login  name	 or  a
		 numeric userid.  The default user name is `unknown'.

   Options
       Examine	 and  files  in	 the  current directory instead of the default
		 ones.

       Specify this option when
		 is unable to find your configuration file, or when  you  sus‐
		 pect  that  is	 using	the wrong file.	 inet_conf is the path
		 name of the configuration file	 whose	entries	 you  want  to
		 examine.

EXAMPLES
       To predict how would handle a telnet request from the local system:

       The same request, pretending that hostname lookup failed:

       To predict what would do when the client name does not match the client
       address:

AUTHOR
	      Wietse Venema (wietse@wzv.win.tue.nl),
	      Department of Mathematics and Computing Science,
	      Eindhoven University of Technology
	      Den Dolech 2, P.O. Box 513,
	      5600 MB Eindhoven, The Netherlands

FILES
       The default locations of the access control tables are:

       (daemon, client) pairs that are granted access.

       (daemon, client) pairs that are denied access.

SEE ALSO
       tcpdchk(1), configuration checker.

       inetd.conf(4), format of the inetd control file.

       hosts_access(5), format of the access control tables.

       hosts_options(5), format of the language extensions.

								  tcpdmatch(1)
[top]

List of man pages available for HP-UX

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net