First of all I'd like to apologise if I posted in the wrong forum, this might belong to software.

I decided to install an Ident-daemon on my router and since I didn't have access to my slackware-disks (running Slackware 9) I downloaded pidentd 3.0.18 (from [can't post the URL but the first hit when searching for "pidentd" on google]), compiled and installed.

Since I didn't want to reboot the machine I added a line in my bootscripts to start the daemon (don't use Inetd) and then manually started it using "/usr/sbin/identd -b -n". (-b stands for stand-alone mode).

And now when I do "ps aux" I have 7 identd processes running. I thought that I might have done something wrong so I killed all the identd processes and again started the daemon with the same result.

So I'm wondering if any of you might know why there are 7 of them running and if it's necessary, and, if not, how to prevent it.

All help welcome.
--
Yorthen

The latest pidentd versions use multithreading, so this would more or less seem normal. If you want to send the list of processes showing up, that would help alot.

Regards,
David

From "ps aux":

USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
nobody 12379 0.0 2.6 13104 992 ? S 17:07 0:00 /usr/sbin/identd -b -n
nobody 12380 0.0 2.6 13104 992 ? S 17:07 0:00 /usr/sbin/identd -b -n
nobody 12381 0.0 2.6 13104 992 ? S 17:07 0:00 /usr/sbin/identd -b -n
nobody 12382 0.0 2.6 13104 992 ? S 17:07 0:00 /usr/sbin/identd -b -n
nobody 12383 0.0 2.6 13104 992 ? S 17:07 0:00 /usr/sbin/identd -b -n
nobody 12384 0.0 2.6 13104 992 ? S 17:07 0:00 /usr/sbin/identd -b -n
nobody 12385 0.0 2.6 13104 992 ? S 17:07 0:00 /usr/sbin/identd -b -n


Since (IIRC) Linux does not have any nativ support for threads it would have to be implemented as user-space threads, which should mean that each program using threads manages them internally. The effect should be the same though; only one process.