Subject: Re: CVS commit: src (identd -L)
To: Jim Wise <email@example.com>
From: Andrew Brown <firstname.lastname@example.org>
Date: 05/18/1999 21:34:20
>Not necessarily. This is the behavior if you start identd with `wait'
>in inetd.conf, and use the `-w' flag. identd can also be run with
>`nowait' if it is started without `-w' or with the `-i' flag. From the
> 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
well...there is always this, but a lot of people don't usually go that
far into hacking on their inetd.conf files. they comment stuff out,
they uncomment stuff, they might even add stuff (or insert tcpd in the
right places), but they usually don't change stuff.
>There is a strong argument that the (commented out) identd line in
>src/etc/inetd.conf should use `nowait' -- if no one objects, I'll change
i'll second that. but i'm still not gonna use it. :)
>> print("$your , $mine : USERID : UNIX :george\r\n");
>>this is my identd, which runs as a "nowait" service. the problem is,
>>of course, that it will hang if the "client" to identd doesn't say
>Yup. Also, it's not clear to me that the perl interpreter is any
>lighter weight than identd -L's fast path, when identd is started
>nowait. Same goal - different way of getting there. :)
oh...i'm sure there's a lot more overhead, but this was good for me in
a pinch where i needed to "provide" the info to someone but didn't
want to actually give them the info.
|-----< "CODE WARRIOR" >-----|
email@example.com * "ah! i see you have the internet
firstname.lastname@example.org (Andrew Brown) that goes *ping*!"
email@example.com * "information is power -- share the wealth."