protocol failure in circuit setup Post: 302319285

Sponsored Content

Top Forums UNIX for Advanced & Expert Users protocol failure in circuit setup Post 302319285 by peterr on Monday 25th of May 2009 01:21:24 AM

05-25-2009

Registered User

inetd does rate-limiting. By default it stops at 40 connections per minute and then "punishes" you with 10 minutes of not listening anymore.

In /etc/inetd.conf, try this:

shell stream tcp nowait.1000 root /usr/sbin/tcpd in.rshd -L

Instead of this:

shell stream tcp nowait root /usr/sbin/tcpd in.rshd -L

For xinetd, there are more options (and more explicit):

cps

Limits the rate of incoming connections. Takes two arguments. The first argument is the number of connections per second to handle. If the rate of incoming connections is higher than this, the service will be temporarily disabled. The second argument is the number of seconds to wait before re-enabling the service after it has been disabled. The default for this setting is 50 incoming connections and the interval is 10 seconds.

max_load

Takes a floating point value as the load at which the service will stop accepting connections. For example: 2 or 2.5. The service will stop accepting connections at this load. This is the one minute load average. This is an OS dependent feature, and currently only Linux, Solaris, and FreeBSD are supported for this. This feature is only avaliable if xinetd was configured with the -with-load-avg option.

peterr

View Public Profile for peterr

Find all posts by peterr

6 More Discussions You Might Find Interesting

1. AIX

NIM server setup on etherchannel setup environment

I know that IBM's official stance is that NIM does not work on etherchannel environment, but has anyone able to get around it? I'm working on a p5-590 LPAR system, and the NIM master and clients are all on the same frame. Any help is appreciated.

2. Homework & Coursework Questions

USB Circuit Question

My problem is I need to control a 7 segment LED circuit (currently on a breadboard, eventually on a PCB). The only option I have from my PC is through USB. The circuit I have built on a breadboard uses 7 segment LED's and 4206 decade counters. I have cut a USB cable in half, and am using the...

3. UNIX for Dummies Questions & Answers

boot up failure unix sco after power failure

hi power went out. next day unix sco wont boot up error code 303. any help appreciated as we are clueless.

4. Shell Programming and Scripting

Short circuit if

Hello everyone, just wondering if this type of if condition will execute properly. Suppose I have a script with two functions in it called abc and def: is this code valid, or is there a better way to short circuit the if statement? #! /bin/ksh93 abc(){ statement 1 using $1 statement 2...

5. UNIX and Linux Applications

UNIX Circuit Design System

Hi all. In some articles I have read about a "UNIX Circuit Design System", which was written originally in some version of Research UNIX by Sandy Fraser. Here is a quote from the article "A Research UNIX Reader: Annotated Excerpts from the Programmer's Manual", by Douglas McIlroy: Even...

6. Answers to Frequently Asked Questions

Running Turbo-cad and circuit wizard programmes.

Hi. i am new to Linux. i have a Turbo-cad and circuit wizard programme on CD that I want to install and run. I keep getting the message I do not have an auto-run programme. Do I need to install specific drivers for this? What programme do I need?

LEARN ABOUT FREEBSD

rsh

RSH(1)							    BSD General Commands Manual 						    RSH(1)

NAME

     rsh -- remote shell

SYNOPSIS

     rsh [-46dn] [-l username] [-t timeout] host [command]

DESCRIPTION

     The rsh utility executes command on host.

     The rsh utility copies its standard input to the remote command, the standard output of the remote command to its standard output, and the
     standard error of the remote command to its standard error.  Interrupt, quit and terminate signals are propagated to the remote command; rsh
     normally terminates when the remote command does.	The options are as follows:

     -4    Use IPv4 addresses only.

     -6    Use IPv6 addresses only.

     -d    Turn on socket debugging (using setsockopt(2)) on the TCP sockets used for communication with the remote host.

     -l username
	   Allow the remote username to be specified.  By default, the remote username is the same as the local username.  Authorization is deter-
	   mined as in rlogin(1).

     -n    Redirect input from the special device /dev/null (see the BUGS section of this manual page).

     -t timeout
	   Allow a timeout to be specified (in seconds).  If no data is sent or received in this time, rsh will exit.

     If no command is specified, you will be logged in on the remote host using rlogin(1).

     Shell metacharacters which are not quoted are interpreted on local machine, while quoted metacharacters are interpreted on the remote
     machine.  For example, the command

	   rsh otherhost cat remotefile >> localfile

     appends the remote file remotefile to the local file localfile, while

	   rsh otherhost cat remotefile ">>" other_remotefile

     appends remotefile to other_remotefile.

FILES

     /etc/hosts

SEE ALSO

     rlogin(1), setsockopt(2), rcmd(3), ruserok(3), hosts(5), hosts.equiv(5), rlogind(8), rshd(8)

HISTORY

     The rsh command appeared in 4.2BSD.

BUGS

     If you are using csh(1) and put a rsh in the background without redirecting its input away from the terminal, it will block even if no reads
     are posted by the remote command.	If no input is desired you should redirect the input of rsh to /dev/null using the -n option.

     You cannot run an interactive command (like ee(1) or vi(1)) using rsh; use rlogin(1) instead.

     Stop signals stop the local rsh process only; this is arguably wrong, but currently hard to fix for reasons too complicated to explain here.

BSD
								 October 16, 2002							       BSD