On Tue, Mar 10, 1998 at 08:01:28AM -0600, Craig Kattner wrote:
> In my logs I have entry after entry like this:
>
> Mar 10 01:04:13 Tarats inetd[11056]: execv /usr/sbin/in.identd: No such
> file or directory
> Mar 10 01:16:26 Tarats inetd[11061]: execv /usr/sbin/in.identd: No such
> file or directory
> Mar 10 01:24:34 Tarats inetd[11066]: execv /usr/sbin/in.identd: No such
> file or directory
> Mar 10 01:28:38 Tarats inetd[11071]: execv /usr/sbin/in.identd: No such
> file or directory
>
> Indeed this file is not present. These warnings go back for months. What
> do they mean? Or more specifically, what does in.identd do and where
> should it have come from?
The quick answer to eliminate the warning is to comment out the
auth line in /etc/inetd.conf and "killall -HUP inetd". As to what
these message mean. Well, the identd man page say
"identd operates by looking up specific TCP/IP connections
and returning the user name of the process owning the connection."
So basically some user on your machine (maybe you) is connecting to another
machine for ftp, telnet, sendmail, or whatever and then some process on the
remote machine is making an auth request to see who started the connection
on your end. inetd answers port 113 (auth) and tries to start in.identd
as it has been instructed in /etc/inetd.conf. When is doesn't find in.identd
it generates this error.
Greg Whittier
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject.
