Sponsored Content
Full Discussion: Non Profit UNIX Foundation
Contact Us Post Here to Contact Site Administrators and Moderators Non Profit UNIX Foundation Post 36919 by Perderabo on Friday 6th of June 2003 09:49:23 PM
Old 06-06-2003
Heh, It pays to be paranoid... Smilie
 

4 More Discussions You Might Find Interesting

1. Linux

GNU's Not Unix! - The Free Software Foundation

The GNU Project: http://www.gnu.org/ (20 Replies)
Discussion started by: Neo
20 Replies

2. Windows & DOS: Issues & Discussions

Microsoft Team Foundation Server (TFS) for Unix source files

Hi, I am using Microsoft Team Foundation server as Configuration management tool for the .NET projects in our team. I would like to add my Unix source files to TFS. Please let me know how can i use TFS for version control of my Unix source files? Thanks for your help (0 Replies)
Discussion started by: rameshmelam
0 Replies

3. Shell Programming and Scripting

Poker: calc profit in tournaments

Imagine that you play poker and the file 1.txt is your buy-in, and in 2.txt is your gains. I want to know the tournament that have more proffit and less proffit. 1.txt aa:1000 bb:2000 cc:3000 dd:4000 ee:5000 2.txt aa:0 bb:1000 cc:1500 dd:3000 ee:2000 Result: dd more profit; aa... (5 Replies)
Discussion started by: rafazz
5 Replies

4. UNIX for Dummies Questions & Answers

Access of Microsoft Team Foundation Server (TFS) repository from Unix Server

Hello, Some of our application team uses Microsoft Team Foundation server (TFS) reposity tool for their .NET projects , I would like to access it form Unix/Linux machine. Please let me know how can access the TFS from unix. Thanks (0 Replies)
Discussion started by: posix
0 Replies
TCPDMATCH(8)						      System Manager's Manual						      TCPDMATCH(8)

NAME
tcpdmatch - tcp wrapper oracle SYNOPSIS
tcpdmatch [-d] [-i inet_conf] daemon client tcpdmatch [-d] [-i inet_conf] daemon[@server] [user@]client DESCRIPTION
tcpdmatch predicts how the tcp wrapper would handle a specific request for service. Examples are given below. The program examines the tcpd access control tables (default /etc/hosts.allow and /etc/hosts.deny) and prints its conclusion. For maximal accuracy, it extracts additional information from your inetd network configuration file. When tcpdmatch finds a match in the access control tables, it identifies the matched rule. In addition, it displays the optional shell com- mands or options in a pretty-printed format; this makes it easier for you to spot any discrepancies between what you want and what the pro- gram understands. ARGUMENTS
The following two 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, tcpdmatch gives a prediction for each address listed for that client. When a client address is specified, tcpdmatch predicts what tcpd would do when client name lookup fails. Optional information specified with the daemon@server 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 user@client form: user A client user identifier. Typically, a login name or a numeric userid. The default user name is `unknown'. OPTIONS
-d Examine hosts.allow and hosts.deny files in the current directory instead of the default ones. -i inet_conf Specify this option when tcpdmatch is unable to find your inetd.conf network configuration file, or when you suspect that the pro- gram uses the wrong one. EXAMPLES
To predict how tcpd would handle a telnet request from the local system: tcpdmatch in.telnetd localhost The same request, pretending that hostname lookup failed: tcpdmatch in.telnetd 127.0.0.1 To predict what tcpd would do when the client name does not match the client address: tcpdmatch in.telnetd paranoid On some systems, daemon names have no `in.' prefix, or tcpdmatch may need some help to locate the inetd configuration file. FILES
The default locations of the tcpd access control tables are: /etc/hosts.allow /etc/hosts.deny SEE ALSO
tcpdchk(8), tcpd configuration checker hosts_access(5), format of the tcpd access control tables. hosts_options(5), format of the language extensions. inetd.conf(5), format of the inetd control file. AUTHORS
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 TCPDMATCH(8)
All times are GMT -4. The time now is 03:44 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy