Have you tried specifiying a different 'max' value after the wait
	or nowait option (ie 'nowait.100') then restarting inetd - the
	default is a max of 40 instances per minute.

	Unless the problem is in the teleporter / socket end - can you
	enable logging to confirm each telporter is starting up ok?

		David/abs	david@{mono.org,southern.com,mhm-internet.com}

System Manager: Southern Studios Ltd, PO Box 59, London N22 1AR.
Satisfied User: NetBSD, free Un*x {i386,sparc,mac68k,+more} 'www.netbsd.org'.
  System Admin: MHM Internet, 14 Barley Mow Passage, Chiswick, London W4 4PH.
         SysOP: Monochrome, Largest UK Internet BBS - 'telnet mono.org'.

On Mon, 4 Nov 1996, Jukka Marin wrote:

> I have a special server which is run by inetd.  Every once in a while I get
> this in syslog:
> 
>   Nov  4 17:37:58 goofy inetd[93]: teleporter/tcp server failing (looping),
>                   service terminated
> 
> After this, my syslog is flooded with
> 
>   Nov  4 17:47:58 goofy inetd[93]: teleporter/tcp: bind: Address already in use
> 
> The only way to make the server work again is to reboot the system.  What is
> my server doing wrong?  It shouldn't be 'looping' in any way - it is possible
> that lots of server processes are started within a short period of time, but
> this can't be helped.
> 
> Any help?
> 
>   -jm
> 
> -- 
> 
>                      ---> http://www.jmp.fi/~jmarin/ <---
>