Re: [TCLUG:16531] identd problems.

[rhankins@d.umn.edu]

* Eric F Crist <ecrist@ardent-hacker.net> [000421 10:12]:
> Ok,
> 
> I'm sick of this.  I've recently downloaded the newest version of identd (don't
> remeber what the version was).  I downloaded in order to fix a problem where,
> when my computer's been running for a day or so, I end up with about 75
> instances of the line:
> root     20407  0.0  0.5  1372  672 ?        S    07:17   0:00 identd -i  

Well, it's hard to say without knowing exactly what identd you're
running, and seeing the entry in /etc/inetd.conf for identd.  My guess
is that you're omitting an option like this one:

[man identd on Slackware]
...
The  -i  flag,  which  is the default mode, should be used
when starting the daemon  from  inetd  with  the  "nowait"
option  in the /etc/inetd.conf file. Use of this mode will
make inetd start one identd  daemon  for  each  connection
request.

The  -w  flag should be used when starting the daemon from
inetd with the "wait" option in the /etc/inetd.conf file .
This  is  the  prefered  mode of operation since that will
start a copy of identd at the first connection request and
then identd will handle subsequent requests without having
to do the nlist  lookup  in  the  kernel  file  for  every
request  as  in  the -i mode above. The identd daemon will
run either forever, until a bug makes it crash or a  time-
out, as specified by the -t flag, occurs.
...

If you're omitting the -w nowait the nowait option in /etc/inetd.conf, it's
possible that you'd get results like these.

What is the entry in your inetd.conf?

-R

-- 
-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^
Ryan Hankins       University Of Minnesota, Duluth
-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^