On Jun 12, Michael Meskes wrote: > I get quite a lot of these messages: > > inetd[153]: ident/tcp server failing (looping), service terminated > > How can I tell which service is the one that's asked for too often?
Have you tried the -l (and maybe the -d) option of the identd? BTW: Never ever use the tcp_wrapper for the identd (you'll get a nice tcpd->identd->tcpd->... loop). You could also check (and count) the "connect" messages from the tcp_wrapper in /var/log/daemon.log. Another possibility would be to start inetd with the -d option. > I tried tcplogd but all tcp requests logged are to auth and www-proxy both > of which are not in /etc/inetd.conf. I don't know how auth is handled, is it > an internal service? www-proxy was added by myself and points to a squid > daemon so inetd shouldn't get a hand on it, or does it? If squid receives a request from a local user and squid wants to check the identity it will call the local ident/auth service (which will be called by inetd). Thanks, Peter -- Peter Tobias <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> PGP ID EFAA400D, fingerprint = 06 89 EB 2E 01 7C B4 02 04 62 89 6C 2F DD F1 3C -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
