> Jukka Marin writes:
>>  Nov  4 17:37:58 goofy inetd[93]: teleporter/tcp server failing (looping),
>>                  service terminated
> 
>> 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.
> 
> inetd's default is that if it starts a service more than 40 times in a
> minute - it must be looping (ie. terminating early).

While we're on this topic ...

I find that if I do a "rusers -l" on my local network, my own NetBSD/SPARC 1.2
system (not -current) will oftentimes fail similarly:

messages:Nov  8 10:25:09 netbsd4me inetd[138]: rusersd/rpc/udp server failing
 (looping), service terminated 
messages:Nov  8 10:40:29 netbsd4me inetd[138]: rusersd/rpc/udp server failing
 (looping), service terminated 
messages:Nov  8 13:58:16 netbsd4me inetd[138]: rusersd/rpc/udp server failing
 (looping), service terminated 

Only "rusersd" seems to fail in this manner.  Anyone else ever see this?

	- Greg