At 08:08 AM 5/7/00, Nitin R Gizare wrote:
>Hi all ,
>
>I have redhat 5.2 and I am using cvs 1.10 , pserver method.
>Some times I have problem of connection getting refused to port 2401
> I am restarting the inetd and it works fine .
>/var/log/messages file shows following messages
>May 7 14:16:43 abhinav inetd[259]: 2401/tcp server failing (looping),
>service terminated
>What is the problem ? ,is there any problem with cvs pserver method
Linux:
$ man inetd
INETD(8) System Manager's
Manual INETD(8)
NAME
inetd - internet ``super-server''
SYNOPSIS
inetd [-di] [-q queuelength] [configuration file]
...
The wait/nowait entry is applicable to datagram sockets only
(other sock�
ets should have a ``nowait'' entry in this space). If a
datagram server
...
and then forks and exits to allow inetd to check for new
service requests
--> to spawn new servers. The optional ``max'' suffix (separated from
--> ``wait'' or ``nowait'' by a dot) specifies the maximum number
of server
--> instances that may be spawned from inetd within an interval of
60 sec�
--> onds. When omitted, ``max'' defaults to 40.
Solaris:
$ man inetd
Maintenance Commands inetd(1M)
NAME
inetd - Internet services daemon
SYNOPSIS
inetd [ -d ] [ -s ] [ -t ] [ -r count interval ] [
configuration-file ]
DESCRIPTION
inetd is the server process for the Internet standard ser-
...
OPTIONS
...
-r Allows inetd to detect and then suspend ``broken''
connectionless datagram services servers, for example,
UDP, and RPC/CLTS. Without this detection, a buggy
server that fails before consuming the service request
will be continuously restarted and will tax system
resources too much. The -r flag has the form:
-r count interval
--> count and interval are decimal numbers that represent
--> the maximum count of invocations per interval of
--> seconds a service may be started before the service is
--> considered ``broken.''
--> Once considered ``broken,'' a server is suspended for
--> ten minutes. After ten minutes, inetd again enables
--> service, hoping the server behaves correctly.
If the -r flag is not specified, inetd behaves as
though -r40 60 was specified.
Can this be your problem?
-Garry Williams
>Any help on this is appreciated.
>
>Thanks
>Nitin
