Sponsored Content
Full Discussion: fail to telnet localhost 106
Operating Systems Linux Ubuntu fail to telnet localhost 106 Post 302151612 by reborg on Sunday 16th of December 2007 03:18:22 PM
Old 12-16-2007
Also try without tcp wrappers first:

Code:
poppassd stream tcp nowait root /usr/sbin/poppassd in.poppassd

 

3 More Discussions You Might Find Interesting

1. Linux

Telnet fail

Hi, I try to telnet to server: # telnet xx.xxx.1.72 1521 Trying xx.xxx.1.72... telnet: connect to address xx.xxx.1.72: Connection refused telnet: Unable to connect to remote host: Connection refused iptables is off: # service iptables status Firewall is stopped. # And I have edit... (4 Replies)
Discussion started by: mehrdad68
4 Replies

2. Shell Programming and Scripting

If Telnet fail abort other command..??

Hi Team, I my script i telent my node ip and after loging i run some commands...But some time login fail so i want to stop script at that time.. CONFIG_CHNG.sh printf 'Please Input Node ID : ' read node node="$node" #exec > node_log_$node.log 2>&1 #set -x >... (2 Replies)
Discussion started by: Ganesh Mankar
2 Replies

3. UNIX for Beginners Questions & Answers

Telnet failed to localhost.

Hi, I am trying telnet to localhost 514. But the connection is refusing. Port does not appear in netstat. IP table service is also off. (5 Replies)
Discussion started by: Nishit
5 Replies
micro_proxy(8)						      System Manager's Manual						    micro_proxy(8)

NAME
micro_proxy - really small HTTP/HTTPS proxy SYNOPSIS
micro_proxy DESCRIPTION
micro_proxy is a very small HTTP/HTTPS proxy. It runs from inetd, which means its performance is poor. But for low-traffic sites, it's quite adequate. It implements all the basic features of an HTTP/HTTPS proxy, in only 260 lines of code. To install it, add a line like this to /etc/inetd.conf: webproxy stream tcp nowait nobody /usr/sbin/micro_proxy micro_proxy Make sure the path to the executable is correct. Then add a line like this to /etc/services: webproxy port/tcp Change "port" to the port number you want to use - 3128, or whatever. Then restart inetd by sending it a "HUP" signal, or rebooting. On some systems, inetd has a maximum spawn rate - if you try to run inetd services faster than a certain number of times per minute, it assumed there's either a bug of an attack going on and it shuts down for a few minutes. If you run into this problem - look for syslog messages about too-rapid looping - you'll need to find out how to increase the limit. Unfortunately this varies from OS to OS. On Free- BSD, you add a "-R 10000" flag to inetd's initial command line. On some Linux systems, you can set the limit on a per-service basis in inetd.conf, by changing "nowait" to "nowait.10000". AUTHOR
Copyright (C) 1999 by Jef Poskanzer <jef@mail.acme.com>. All rights reserved. 16 March 1999 micro_proxy(8)
All times are GMT -4. The time now is 02:15 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy